NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

OpenClaw's dashboard leaked gateway auth material via browser URL/query and localStorageGHSA-rchv-x836-w7xp

HIGHFix: openclaw/openclaw@10d0e3f

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.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Mar 9, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
openclawnpm
2.9Mdownloads / 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:

  1. macOS Open Dashboard constructed a URL with auth material.
  2. The browser received that credential-bearing URL.
  3. The Control UI imported the token from the URL.
  4. 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
EcosystemPackageVulnerable rangeFix
📦npmopenclawall versions2026.3.7npm install openclaw@2026.3.7

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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.

  3. 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.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
OpenClaw's dashboard leaked gateway auth material via…