How severe is GHSA-v6x2-2qvm-6gv8?

No CVSS score has been assigned to GHSA-v6x2-2qvm-6gv8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v6x2-2qvm-6gv8?

GHSA-v6x2-2qvm-6gv8 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-v6x2-2qvm-6gv8?

Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6x2-2qvm-6gv8 is resolved across your whole dependency graph.

How do I detect GHSA-v6x2-2qvm-6gv8 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-v6x2-2qvm-6gv8 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-v6x2-2qvm-6gv8?

O3 pinpoints whether GHSA-v6x2-2qvm-6gv8 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-v6x2-2qvm-6gv8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v6x2-2qvm-6gv8 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.

What is the EPSS score for GHSA-v6x2-2qvm-6gv8?

GHSA-v6x2-2qvm-6gv8 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v6x2-2qvm-6gv8?

GHSA-v6x2-2qvm-6gv8 is classified as CWE-320 (CWE-320). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v6x2-2qvm-6gv8 published, and has it been updated?

GHSA-v6x2-2qvm-6gv8 was published on March 3, 2026 and was last updated on March 24, 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-v6x2-2qvm-6gv8

OpenClaw reuses the gateway auth token in the owner ID prompt hashing fallback

Also known asCVE-2026-32897

Published

Mar 3, 2026

Updated

Mar 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk17th percentile+0.20%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

Vulnerability

OpenClaw reused gateway.auth.token (and gateway.remote.token) as a fallback hash secret for owner-ID prompt obfuscation when commands.ownerDisplay=hash and commands.ownerDisplaySecret was unset.

This created secret dual-use between gateway authentication and prompt metadata hashing.

Impact

Auth-secret dual-use across security domains (gateway auth and prompt metadata hashing).
Hash outputs are visible to third-party model providers in system prompts.
No direct plaintext token disclosure.
Practical risk is highest when operators use weak gateway tokens and leave owner hash secret unset.

Affected Packages / Versions

Package: openclaw (npm)
Latest affected published version: 2026.2.21-2
Vulnerable range: <= 2026.2.21-2
Patched version (planned next release): 2026.2.22

Affected Components

src/agents/cli-runner/helpers.ts
src/agents/pi-embedded-runner/run/attempt.ts
src/agents/pi-embedded-runner/compact.ts

Remediation

Added a shared owner-display resolver and secret-generation helper.
Removed fallback to gateway.auth.token and gateway.remote.token.
Auto-generates and persists a dedicated commands.ownerDisplaySecret when hash mode is enabled and secret is missing.

Fix Commit(s)

c99e7696e6893083b256f0a6c88fb060f3a76fb7

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.22). Once npm release 2026.2.22 is published, this advisory only needs to be published.

OpenClaw thanks @aether-ai-agent for reporting.

Affected Packages

1 total 1 fixed

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

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.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6x2-2qvm-6gv8 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-v6x2-2qvm-6gv8 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-v6x2-2qvm-6gv8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Vulnerability OpenClaw reused `gateway.auth.token` (and `gateway.remote.token`) as a fallback hash secret for owner-ID prompt obfuscation when `commands.ownerDisplay=hash` and `commands.ownerDisplaySecret` was unset. This created secret dual-use between gateway authentication and prompt metadata hashing. ## Impact - Auth-secret dual-use across security domains (gateway auth and prompt metadata hashing). - Hash outputs are visible to third-party model providers in system prompts. - No direct plaintext token disclosure. - Practical risk is highest when operators use weak gateway tokens an

O3 Security · Impact-Aware SCA

Is GHSA-v6x2-2qvm-6gv8 in your dependencies?

O3 detects GHSA-v6x2-2qvm-6gv8 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