CVE-2026-35663: OpenClaw: Gateway Backend Reconnect lets Non-Admin Operator Scopes Self-Claim operator.admin
OpenClaw 2026.3.24 and earlier let a backend-labeled gateway client reconnect and ask for broader scopes than it was approved for, skipping pairing. A non-admin operator could come back as operator.admin. The advisory rates it critical. The package data lists no patched version, but the advisory text names 2026.3.25.
Published Mar 27, 2026 · Updated Apr 10, 2026 · Analysis Oct 31, 2026
What an attacker can do
The gateway grants scopes such as operator.read and operator.admin to paired devices. When a paired device reconnects asking for more scopes than its approved baseline, the gateway should require a new pairing approval. In src/gateway/server/ws-connection/, the helper shouldSkipBackendSelfPairing() skipped pairing for local backend clients when shared-secret or device-token auth succeeded and no browser origin header was present.
A backend-labeled reconnect could therefore request operator.admin and get it with no approval. The attacker needs a low-privilege operator credential and network access to the gateway (CWE-269, CWE-863). The result is full operator control of the gateway: read every session, run admin methods, change configuration and use the agents it manages.
The CVSS 4.0 vector scores 9.3 with high confidentiality and integrity impact on the gateway and on connected systems. This is the most serious flaw in the March 2026 OpenClaw batch because it turns a limited token into an admin one.
Who is affected
openclaw 2026.3.24 and earlier. Any gateway where operators or devices hold scopes below operator.admin, and where an attacker can reach the WebSocket port, is at risk. Check the version:
npm ls openclawopenclaw
- Ecosystem
- npm
- Affected
- <= 2026.3.24
- Fixed in
- No patched version yet
- Check
npm ls openclaw
How to fix it
The package data lists no patched version for this entry. The advisory body names 2026.3.25 as the first patched version and the fix commit d3d8e316bd81 is on main, so upgrade to the newest openclaw release and confirm it is 2026.3.25 or later:
npm install openclaw@latestThe commit deletes shouldSkipBackendSelfPairing(), so backend reconnects follow normal pairing and a scope upgrade above the approved baseline now returns "pairing required". Until you upgrade, keep the gateway port off untrusted networks and review issued operator tokens.
How to tell if you were hit
Check the gateway logs and paired device list for devices whose operator scopes changed to operator.admin without an approval you made. Look for backend-labeled reconnects that followed a connection with narrower scopes. On a fixed build the same attempt creates a pending request and a device.pair.requested event listing operator.admin scopes. Rotate operator tokens if you find a silent upgrade.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Gateway Backend Reconnect lets Non-Admin Operator Scopes Self-Claim operator.admin
Affected Packages / Versions
- Package:
openclaw - Affected versions:
<= 2026.3.24 - First patched version:
2026.3.25 - Latest published npm version at verification time:
2026.3.24
Details
Backend-labeled reconnects could previously self-request broader scopes and bypass pairing, allowing non-admin operators to reconnect as operator.admin. Commit d3d8e316bd819d3c7e34253aeb7eccb2510f5f48 removes the backend self-pairing skip and requires pairing when requested scopes exceed the approved baseline.
Verified vulnerable on tag v2026.3.24 and fixed on main by commit d3d8e316bd819d3c7e34253aeb7eccb2510f5f48.
Fix Commit(s)
d3d8e316bd819d3c7e34253aeb7eccb2510f5f48
Credited to zpbrent.
Questions
- Is there a patched version of OpenClaw for CVE-2026-35663?
The package data has none listed. The advisory text says 2026.3.25 and the fix is merged on main in commit d3d8e316bd81. Install the latest release and check its version.
- What does the attacker need?
A valid non-admin operator credential and network access to the gateway. The vector shows low privileges, no user interaction and low complexity.
- How does the fix behave?
A reconnect that asks for scopes beyond the approved baseline now needs pairing approval. It fails with "pairing required" and the stored scopes stay unchanged.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
