https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-09-28T21:57:25.207706+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/cve-2026-53821 CVE-2026-53821 — OpenClaw < 2026.5.18 - Scope Elevation in trusted-proxy Control UI WebSocket 2026-09-28T21:57:25.218393+00:00

Affected: OpenClaw

OpenClaw before 2026.5.18 accepts WebSocket client-declared operator scopes before binding to server-approved pairing or trusted-proxy authorization baseline. Unpaired or restricted trusted-proxy Control UI clients can obtain cached operator.admin authority on live WebSocket connections to execute admin-gated Gateway RPCs.

 https://db.gcve.eu/vuln/ghsa-qjpc-qf9m-xwmr GHSA-qjpc-qf9m-xwmr — OpenClaw: Trusted-proxy Control UI WebSocket accepted client-declared scopes before pairing 2026-09-28T21:57:25.218454+00:00

Affected: npm: openclaw

### Summary

In trusted-proxy Control UI mode, OpenClaw accepted a WebSocket client's declared operator scopes before those scopes were bound to a server-approved pairing or trusted-proxy authorization baseline.

This issue affects trusted-proxy Control UI deployments. It does not apply to shared-secret Control UI sessions, which are treated as trusted operator sessions by design.

### Affected configurations

This affects deployments using `gateway.auth.mode: "trusted-proxy"` for Control UI access where a restricted trusted-proxy user could open a Control UI WebSocket and present a fresh, unpaired device identity with elevated requested scopes.

### Impact

An unpaired or restricted trusted-proxy Control UI client could obtain cached `operator.admin` authority on its live WebSocket connection. That authority could then be used for admin-gated Gateway RPCs until the connection was closed or revalidated.

### Patched Versions

The first stable patched version is `2026.5.18`.

### Mitigations

Upgrade to `openclaw@2026.5.18` or later. Before upgrading, restrict trusted-proxy Control UI access to users who should have the scopes they can request, and restart the gateway after changing trusted-proxy authorization policy.