GHSA-4W7M-58CG-CMFF

In affected versions of openclaw, sandboxed leaf subagents could still access the subagents control surface and resolve against the parent requester scope instead of remaining confined to their own session tree.

Affected Packages and Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.3.8
• Fixed in: 2026.3.11

Technical Details

Leaf subagents retained the subagents tool, and subagent control requests were authorized against the parent requester scope rather than the caller's own spawned descendants. The control path prevented only self-targeting, not cross-sibling steering.

Workarounds

Upgrade to 2026.3.11 or later.

A low-privilege sandboxed leaf worker could steer or kill a sibling run owned by the same requester and cause that sibling to execute with its own broader tool policy. This is a sandbox and session-scope boundary bypass.

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-4W7M-58CG-CMFF has a CVSS score of 8.8 (High). The vector is requires local access, low 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.11); upgrading removes the vulnerable code path.

Kodem intelligence

OpenClaw now removes subagents control access from leaf subagents by default, scopes subagent control to the caller's own descendants, and rejects steer and kill requests that target runs outside that descendant tree. The fix shipped in [email protected].

1. What is GHSA-4W7M-58CG-CMFF? GHSA-4W7M-58CG-CMFF is a high-severity improper privilege management vulnerability in openclaw (npm), affecting versions < 2026.3.11. It is fixed in 2026.3.11. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is GHSA-4W7M-58CG-CMFF? GHSA-4W7M-58CG-CMFF has a CVSS score of 8.8 (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-4W7M-58CG-CMFF? openclaw (npm) versions < 2026.3.11 is affected.
4. Is there a fix for GHSA-4W7M-58CG-CMFF? Yes. GHSA-4W7M-58CG-CMFF is fixed in 2026.3.11. Upgrade to this version or later.
5. Is GHSA-4W7M-58CG-CMFF exploitable, and should I be worried? Whether GHSA-4W7M-58CG-CMFF 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-4W7M-58CG-CMFF 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-4W7M-58CG-CMFF? Upgrade openclaw to 2026.3.11 or later.