Summary
OpenClaw's ACP child sessions inherit subagent security envelope constraints
ACP child sessions inherit subagent security envelope constraints.
Affected Packages / Versions
- Package: openclaw (npm)
- Affected versions: <= 2026.4.21
- Fixed version: 2026.4.22
Fix Commit(s)
- 31160dc069b7cc5d833b39c53736a41ad3befda2
Verification
- The fix commit is contained in the public v2026.4.22 tag.
- [email protected] is published on npm and the compiled package contains the fix.
- Focused regression coverage for this path passed before publication.
OpenClaw thanks @zsxsoft, @qclawer, and @KeenSecurityLab for reporting.
Impact
A restricted subagent spawning an ACP child session could fail to carry forward subagent-only constraints such as depth, child-count limits, control scope, or target-agent restrictions.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
ACP spawn now resolves and persists child subagent envelope fields, enforces maximum depth and active-child caps, and applies the inherited control scope to child ACP sessions.
Frequently Asked Questions
- What is CVE-2026-44997? CVE-2026-44997 is a medium-severity security vulnerability in openclaw (npm), affecting versions <= 2026.4.21. It is fixed in 2026.4.22.
- Which versions of openclaw are affected by CVE-2026-44997? openclaw (npm) versions <= 2026.4.21 is affected.
- Is there a fix for CVE-2026-44997? Yes. CVE-2026-44997 is fixed in 2026.4.22. Upgrade to this version or later.
- Is CVE-2026-44997 exploitable, and should I be worried? Whether CVE-2026-44997 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
- What actually determines whether CVE-2026-44997 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.
- How do I fix CVE-2026-44997? Upgrade
openclawto 2026.4.22 or later.