How severe is GHSA-6x2m-hqfw-hvpj?

No CVSS score has been assigned to GHSA-6x2m-hqfw-hvpj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6x2m-hqfw-hvpj?

GHSA-6x2m-hqfw-hvpj affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-6x2m-hqfw-hvpj?

Update openclaw to 2026.2.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6x2m-hqfw-hvpj is resolved across your whole dependency graph.

How do I detect GHSA-6x2m-hqfw-hvpj 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-6x2m-hqfw-hvpj 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-6x2m-hqfw-hvpj?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6x2m-hqfw-hvpj can be triaged on real exposure rather than presence alone.

Is GHSA-6x2m-hqfw-hvpj actively exploited in the wild?

No public exploit code has been indexed for GHSA-6x2m-hqfw-hvpj 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.

When was GHSA-6x2m-hqfw-hvpj published, and has it been updated?

GHSA-6x2m-hqfw-hvpj was published on March 2, 2026 and was last updated on March 4, 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-6x2m-hqfw-hvpj — openclaw

Fix: openclaw/openclaw@4a3f843

GHSA-6x2m-hqfw-hvpj is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: Node exec approvals could be replayed across nodes

Published

Mar 2, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 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

3.1Mdownloads / week

Description

Summary

exec.approval requests for host=node were not explicitly bound to the target nodeId, so an approval intended for one node could be replayed for a different node under the same operator-controlled gateway fleet.

Impact

An operator approval for a system.run request could be reused across nodes if the request payload did not carry node identity through approval and execution checks.

Affected Packages / Versions

Package: openclaw (npm)
Affected: <= 2026.2.22-2
Fixed: 2026.2.23 (released)

Mitigation

Upgrade to 2026.2.23 or later once published.

Fix Details

The fix requires and persists nodeId for host=node approval requests and rejects execution when the approving node binding does not match the invoking node.

Fix Commit(s)

4a3f8438e527ac371a67fe7ac68a287f0dbe6063

Release Process Note

patched_versions is pre-set to the released version (2026.2.23). This advisory now reflects released fix version 2026.2.23.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.23`npm install openclaw@2026.2.23`

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.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6x2m-hqfw-hvpj 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-6x2m-hqfw-hvpj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6x2m-hqfw-hvpj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary `exec.approval` requests for `host=node` were not explicitly bound to the target `nodeId`, so an approval intended for one node could be replayed for a different node under the same operator-controlled gateway fleet. ## Impact An operator approval for a `system.run` request could be reused across nodes if the request payload did not carry node identity through approval and execution checks. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `<= 2026.2.22-2` - Fixed: `2026.2.23` (released) ## Mitigation Upgrade to `2026.2.23` or later once published. ## Fix D

O3 Security · Impact-Aware SCA

Is GHSA-6x2m-hqfw-hvpj in your dependencies?

O3 Security finds GHSA-6x2m-hqfw-hvpj 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