GHSA-rchv-x836-w7xp: OpenClaw's dashboard leaked gateway auth material via browser URL/query and localStorage
OpenClaw's macOS Dashboard flow exposed Gateway authentication material to browser-controlled surfaces. Before the fix, the macOS app appended the shared Gateway token and password to the Dashboard URL query string when opening the Control UI in the browser. The Control UI then imported the token and persisted it into browser localStorage under openclaw.control.settings.v1.
Published Mar 9, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.3.2
- Fixed in
- 2026.3.7
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
OpenClaw's macOS Dashboard flow exposed Gateway authentication material to browser-controlled surfaces.
Before the fix, the macOS app appended the shared Gateway token and password to the Dashboard URL query string when opening the Control UI in the browser. The Control UI then imported the token and persisted it into browser localStorage under openclaw.control.settings.v1.
This expanded exposure of reusable Gateway admin credentials into browser address-bar/query surfaces and persistent script-readable storage.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published version verified vulnerable:
2026.3.2 - Affected range:
<= 2026.3.2 - Patched version:
>= 2026.3.7
Impact
An attacker with access to browser-controlled surfaces or persistent browser storage could recover a valid Gateway admin token and reuse it against the OpenClaw management interface.
The exposure chain was:
- macOS
Open Dashboardconstructed a URL with auth material. - The browser received that credential-bearing URL.
- The Control UI imported the token from the URL.
- The Control UI persisted the token in
localStorage.
Fix
The fix aligns the macOS Dashboard flow with the safer existing CLI/bootstrap pattern and removes persistent browser token storage:
- macOS Dashboard now passes the Gateway token via URL fragment instead of query parameters.
- macOS Dashboard no longer propagates the shared Gateway password into browser URLs.
- Control UI keeps Gateway tokens in memory only for the current tab.
- Control UI scrubs legacy persisted tokens from
openclaw.control.settings.v1on load. - Regression tests cover fragment transport, password omission, and token-scrubbing behavior.
Fix Commit(s)
10d0e3f3ca92326df0ca071fabffe463742f263c(March 7, 2026)
Release Process Note
npm 2026.3.7 was published on March 8, 2026. This advisory is fixed in the released package.
Thanks @whiter6666 for reporting.
Credited to whiter6666.
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. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-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, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
