How severe is GHSA-474h-prjg-mmw3?

GHSA-474h-prjg-mmw3 has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-474h-prjg-mmw3?

GHSA-474h-prjg-mmw3 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-474h-prjg-mmw3?

Update openclaw to 2026.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-474h-prjg-mmw3 is resolved across your whole dependency graph.

How do I detect GHSA-474h-prjg-mmw3 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-474h-prjg-mmw3 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-474h-prjg-mmw3?

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

Is GHSA-474h-prjg-mmw3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-474h-prjg-mmw3 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-474h-prjg-mmw3 published, and has it been updated?

GHSA-474h-prjg-mmw3 was published on March 3, 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

HIGH severity

GHSA-474h-prjg-mmw3 — openclaw

HIGHFix: openclaw/openclaw@ac11f0a

GHSA-474h-prjg-mmw3 is a high-severity (CVSS 8) vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: Sandboxed sessions_spawn(runtime="acp") bypassed sandbox inheritance and allowed host ACP initialization

Published

Mar 3, 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

2.5Mdownloads / week

Description

Summary

Sandboxed sessions_spawn(runtime="acp") could bypass sandbox inheritance and initialize host-side ACP runtime. The fix now fail-closes ACP spawn from sandboxed requester sessions and rejects sandbox="require" for runtime="acp".

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version at triage time: 2026.3.1 (March 2, 2026)
Vulnerable range: <=2026.3.1
Patched release: 2026.3.2 (released)

Technical Details

Root cause: runtime="subagent" enforced sandbox inheritance, while runtime="acp" did not enforce equivalent sandbox/runtime checks.
Security impact: sandbox-boundary bypass into host-side ACP initialization.
Fixed behavior:
- deny ACP spawn when requester runtime is sandboxed
- deny sessions_spawn with runtime="acp", sandbox="require"
- align sandboxed prompt guidance to avoid advertising blocked ACP paths

Fix Commit(s)

ac11f0af731d41743ba02d8595f4d0fe747336e3
c703aa0fe92df9fb71cf254fc46991e05fba2114

Affected Packages

1 total 1 fixed

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

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

Tailored to GHSA-474h-prjg-mmw3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Sandboxed `sessions_spawn(runtime="acp")` could bypass sandbox inheritance and initialize host-side ACP runtime. The fix now fail-closes ACP spawn from sandboxed requester sessions and rejects `sandbox="require"` for `runtime="acp"`. ### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version at triage time: `2026.3.1` (March 2, 2026) - Vulnerable range: `<=2026.3.1` - Patched release: `2026.3.2` (released) ### Technical Details - Root cause: `runtime="subagent"` enforced sandbox inheritance, while `runtime="acp"` did not enforce equivalent sandbox

O3 Security · Impact-Aware SCA

Is GHSA-474h-prjg-mmw3 in your dependencies?

O3 Security finds GHSA-474h-prjg-mmw3 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