# CVE-2026-22168: OpenClaw < 2026.2.21 - Command Injection via cmd.exe /c Trailing Arguments in system.run

> Authenticated operators can execute arbitrary commands on Windows nodes by smuggling arguments through cmd.exe /c in OpenClaw's system.run function.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-5v6x-rfc3-7qfr, MINI-933h-g359-3h95

## What is CVE-2026-22168?

CVE-2026-22168 is a high-severity command injection vulnerability in Openclaw Openclaw, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw versions prior to 2026.2.21 contain an approval-integrity mismatch vulnerability in system.run that allows authenticated operators to execute arbitrary trailing arguments after cmd.exe /c while approval text reflects only a benign command. Attackers can smuggle malicious arguments through cmd.exe /c to achieve local command execution on trusted Windows nodes with mismatched audit logs.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-22168?

2 open source packages ship an affected version, including openclaw. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.2.21 |
| `openclaw` | npm | All versions | 2026.2.21 |

Products: Openclaw Openclaw.

## How do I fix CVE-2026-22168?

Upgrade openclaw to 2026.2.21 or later.

## Is CVE-2026-22168 being exploited?

There is no known exploitation of CVE-2026-22168 in the wild and no public exploit code.

## Other vulnerabilities in Openclaw Openclaw

- [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9)
- [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8)
- [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4)
- [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4)
- [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22168 and fix it if it is affected.

What it is: CVE-2026-22168 is a high-severity command injection vulnerability in Openclaw Openclaw, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22168 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.2.21
- openclaw (npm): affected all versions; fixed in 2026.2.21

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22168/ (Markdown: https://insights.sbomify.com/CVE-2026-22168/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22168
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22168
- OSV: https://osv.dev/vulnerability/CVE-2026-22168

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22168/
Summaries are generated and may contain mistakes; the official description above is the record.