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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v6x2-2qvm-6gv8 can be triaged on real exposure rather than presence alone.

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.5%, placing it in the 37th 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

Not in CISA KEV

GHSA-v6x2-2qvm-6gv8 — openclaw

Fix: openclaw/openclaw@c99e769

GHSA-v6x2-2qvm-6gv8 is a CWE-320 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

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

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v6x2-2qvm-6gv8.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

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.

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.5Mdownloads / 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`npm install openclaw@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v6x2-2qvm-6gv8 can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-v6x2-2qvm-6gv8 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works