Summary
OpenClaw has Windows system.run approval mismatch on cmd.exe /c trailing arguments
A Windows system.run approval-integrity mismatch in the cmd.exe /c path could allow trailing arguments to execute while approval/audit text reflected only a benign command string.
This requires an authenticated operator context using the approvals flow and a trusted Windows node.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published vulnerable version (as of 2026-02-21):
2026.2.19-2 - Vulnerable range:
<=2026.2.19-2 - Patched version (planned next release):
2026.2.21
Attack Scenario
- An authenticated operator approval is created for a benign command text (for example,
echo). - A
system.runrequest usescmd.exe /cwith extra trailing arguments. - Prior behavior could bind approval/audit text to the benign command while still executing the full argument tail on the node.
Fix Commit(s)
6007941f04df1edcca679dd6c95949744fdbd4df
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.21). Once that npm release is live, this advisory can be published directly.
OpenClaw thanks @tdjackey for reporting.
Impact
- Local command execution on the trusted Windows node process account.
- Approval/audit command text integrity mismatch.
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.
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
- Canonicalize the full command tail after
cmd.exe /c. - Reuse one shared command canonicalization/validation path for validation, approval matching, and execution/audit text.
- Add regression coverage for trailing-argument smuggling and approval binding.
Frequently Asked Questions
- What is CVE-2026-22168? CVE-2026-22168 is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.2.21. It is fixed in 2026.2.21. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of openclaw are affected by CVE-2026-22168? openclaw (npm) versions < 2026.2.21 is affected.
- Is there a fix for CVE-2026-22168? Yes. CVE-2026-22168 is fixed in 2026.2.21. Upgrade to this version or later.
- Is CVE-2026-22168 exploitable, and should I be worried? Whether CVE-2026-22168 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-22168 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-22168? Upgrade
openclawto 2026.2.21 or later.