How severe is GHSA-rchv-x836-w7xp?

GHSA-rchv-x836-w7xp has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rchv-x836-w7xp?

GHSA-rchv-x836-w7xp affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-rchv-x836-w7xp?

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.

How do I detect GHSA-rchv-x836-w7xp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rchv-x836-w7xp if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-rchv-x836-w7xp?

O3 pinpoints whether GHSA-rchv-x836-w7xp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rchv-x836-w7xp actively exploited in the wild?

No public exploit code has been indexed for GHSA-rchv-x836-w7xp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-rchv-x836-w7xp published, and has it been updated?

GHSA-rchv-x836-w7xp was published on March 9, 2026 and was last updated on March 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-rchv-x836-w7xp

HIGH

OpenClaw's dashboard leaked gateway auth material via browser URL/query and localStorage

Published

Mar 9, 2026

Updated

Mar 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

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 Dashboard constructed 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.v1 on 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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-rchv-x836-w7xp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

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 p

O3 Security · Impact-Aware SCA

Is GHSA-rchv-x836-w7xp in your dependencies?

O3 detects GHSA-rchv-x836-w7xp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works