GHSA-474H-PRJG-MMW3

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

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

GHSA-474H-PRJG-MMW3 has a CVSS score of 8.0 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.3.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-474H-PRJG-MMW3? GHSA-474H-PRJG-MMW3 is a high-severity improper privilege management vulnerability in openclaw (npm), affecting versions <= 2026.3.1. It is fixed in 2026.3.2. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is GHSA-474H-PRJG-MMW3? GHSA-474H-PRJG-MMW3 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by GHSA-474H-PRJG-MMW3? openclaw (npm) versions <= 2026.3.1 is affected.
4. Is there a fix for GHSA-474H-PRJG-MMW3? Yes. GHSA-474H-PRJG-MMW3 is fixed in 2026.3.2. Upgrade to this version or later.
5. Is GHSA-474H-PRJG-MMW3 exploitable, and should I be worried? Whether GHSA-474H-PRJG-MMW3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-474H-PRJG-MMW3 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-474H-PRJG-MMW3? Upgrade openclaw to 2026.3.2 or later.