GHSA-rchv-x836-w7xp is a high-severity (CVSS 7.1) vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw's dashboard leaked gateway auth material via browser URL/query and localStorage
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.3.7npm install openclaw@2026.3.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.3.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rchv-x836-w7xp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rchv-x836-w7xp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-rchv-x836-w7xp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rchv-x836-w7xp in your dependencies?
O3 Security finds GHSA-rchv-x836-w7xp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.