Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-rchv-x836-w7xp

HighCVSS 7.1 / 10
Published Mar 9, 2026·Last modified Mar 9, 2026
Affected Components(0)

No affected components available

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.

Risk Scores
Base Score
7.1

The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data.

Threat Intelligence
6.5

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

High severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard