OpenClaw has Windows system.run approval mismatch on cmd.exe /c trailing arguments
CVE-2026-22168GHSA-5v6x-rfc3-7qfr
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.2.21), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm openclaw
- Affected
- < 2026.2.21
- Fixed in
- 2026.2.21
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-5v6x-rfc3-7qfr lists affected ranges: npm openclaw >=0 <2026.2.21 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-5v6x-rfc3-7qfr lists affected ranges: npm openclaw >=0 <2026.2.21
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.5 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-22168: 0.42% estimated exploitation activity in the next 30 days; percentile 36.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 1. An authenticated operator approval is created for a benign command text (for example, echo). 2. A system.run request uses cmd.exe /c with extra trailing arguments. 3. 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.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-5v6x-rfc3-7qfr
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-5v6x-rfc3-7qfr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-22168 Advisory: OpenClaw has Windows system.run approval mismatch on cmd.exe /c trailing arguments IDs: CVE-2026-22168, GHSA-5v6x-rfc3-7qfr Record: https://patchnext.com/advisories/cve-2026-22168 (revision 3, source checked 26 Oct 2026, 12:46 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.2.21. A vendor fix does not mean a deployment is fixed. ## Affected components - npm openclaw: affected < 2026.2.21; fixed in 2026.2.21 ## Suggested inspection (read-only) - `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on openclaw. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-5v6x-rfc3-7qfr (OSV record GHSA-5v6x-rfc3-7qfr lists affected ranges: npm openclaw >=0 <2026.2.21 (fixed)) - Verified: https://github.com/advisories/GHSA-5v6x-rfc3-7qfr (GitHub-reviewed advisory GHSA-5v6x-rfc3-7qfr lists affected ranges: npm openclaw >=0 <2026.2.21) Commands are suggestions: review each one before running it.
Loading voting…