OpenClaw has Windows system.run approval mismatch on cmd.exe /c trailing arguments
Summary
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.
Impact
- Local command execution on the trusted Windows node process account.
- Approval/audit command text integrity mismatch.
Fix
- 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.
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.
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.