Summary
A wrapper-depth parsing mismatch in system.run allowed nested transparent dispatch wrappers (for example repeated /usr/bin/env) to suppress shell-wrapper detection while still matching allowlist resolution. In security=allowlist + ask=on-miss, this could bypass the expected approval prompt for shell execution.
Severity / Trust Model
OpenClaw’s documented model treats authenticated gateway callers as trusted operators and exec approvals as operator guardrails. This issue is still a real approval-boundary bypass and is triaged as Medium in that model.
Technical Details
- Dispatch-wrapper unwrapping stopped at
MAX_DISPATCH_WRAPPER_DEPTH. - Shell-wrapper extraction could return non-wrapper once depth was exhausted.
- Allowlist resolution could still succeed on partially unwrapped argv beginning with
/usr/bin/env. - Result: nested wrapper chains could execute
/bin/sh -c ...without fresh approval inallowlist+ask=on-miss.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published version at triage time:
2026.2.23 - Vulnerable versions:
<= 2026.2.23 - Patched versions (planned next release):
>= 2026.2.24
Fix Commit(s)
57c9a18180c8b14885bbd95474cbb17ff2d03f0b
Verification
- Added regression coverage for depth-overflow wrapper chains at resolution and
system.runinvocation layers. - Reproduced previous PoC behavior before fix, then confirmed denial after fix with
SYSTEM_RUN_DENIED: approval required.
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.24) so once npm publish is complete, advisory publication can proceed without additional version edits.
OpenClaw thanks @tdjackey for reporting.
Publication Update (2026-02-25)
[email protected] is published on npm and contains the fix commit(s) listed above. This advisory now marks >= 2026.2.24 as patched.
Impact
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
CVE-2026-32023 has a CVSS score of 8.8 (Medium). The vector is network-reachable, 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.2.24); upgrading removes the vulnerable code path.
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.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-32023? CVE-2026-32023 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.23. It is fixed in 2026.2.24. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- How severe is CVE-2026-32023? CVE-2026-32023 has a CVSS score of 8.8 (Medium). 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.
- Which versions of openclaw are affected by CVE-2026-32023? openclaw (npm) versions <= 2026.2.23 is affected.
- Is there a fix for CVE-2026-32023? Yes. CVE-2026-32023 is fixed in 2026.2.24. Upgrade to this version or later.
- Is CVE-2026-32023 exploitable, and should I be worried? Whether CVE-2026-32023 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-32023 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-32023? Upgrade
openclawto 2026.2.24 or later.