How severe is GHSA-6xg4-82hv-cp6f?

No CVSS score has been assigned to GHSA-6xg4-82hv-cp6f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6xg4-82hv-cp6f?

GHSA-6xg4-82hv-cp6f affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-6xg4-82hv-cp6f?

Update openclaw to 2026.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xg4-82hv-cp6f is resolved across your whole dependency graph.

How do I detect GHSA-6xg4-82hv-cp6f 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-6xg4-82hv-cp6f 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-6xg4-82hv-cp6f?

O3 pinpoints whether GHSA-6xg4-82hv-cp6f 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-6xg4-82hv-cp6f actively exploited in the wild?

No public exploit code has been indexed for GHSA-6xg4-82hv-cp6f 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 type of vulnerability is GHSA-6xg4-82hv-cp6f?

GHSA-6xg4-82hv-cp6f is classified as CWE-807 (CWE-807). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6xg4-82hv-cp6f published, and has it been updated?

GHSA-6xg4-82hv-cp6f was published on March 31, 2026 and was last updated on April 20, 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-6xg4-82hv-cp6f

Fix: openclaw/openclaw@4b95427

GHSA-6xg4-82hv-cp6f is a CWE-807 vulnerability in openclaw. O3 Security confirms whether GHSA-6xg4-82hv-cp6f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Gateway chat.send ACP-only provenance guard could be bypassed by client identity spoofing

Also known asCVE-2026-41299

Published

Mar 31, 2026

Updated

Apr 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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-6xg4-82hv-cp6f.

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.

139other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

3.1Mdownloads / week

Description

Summary

ACP-only provenance fields in chat.send were gated by self-declared client metadata from the WebSocket handshake rather than verified authorization state.

Impact

A normal authenticated operator client could spoof ACP identity labels and inject reserved provenance fields intended only for the ACP bridge.

Affected Component

src/gateway/server-methods/chat.ts, src/gateway/server/ws-connection/message-handler.ts

Fixed Versions

Affected: <= 2026.3.24
Patched: >= 2026.3.28
Latest stable 2026.3.28 contains the fix.

Fix

Fixed by commit 4b9542716c (Gateway: require verified scope for chat provenance).

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Summary ACP-only provenance fields in `chat.send` were gated by self-declared client metadata from the WebSocket handshake rather than verified authorization state. ## Impact A normal authenticated operator client could spoof ACP identity labels and inject reserved provenance fields intended only for the ACP bridge. ## Affected Component `src/gateway/server-methods/chat.ts, src/gateway/server/ws-connection/message-handler.ts` ## Fixed Versions - Affected: `<= 2026.3.24` - Patched: `>= 2026.3.28` - Latest stable `2026.3.28` contains the fix. ## Fix Fixed by commit `4b9542716c` (`Gat

O3 Security · Impact-Aware SCA

Is GHSA-6xg4-82hv-cp6f in your dependencies?

O3 detects GHSA-6xg4-82hv-cp6f 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