# CVE-2026-22176: OpenClaw has a Command Injection via unescaped environment assignments in Windows Scheduled Task script generation

> Attackers can execute arbitrary commands on Windows systems by injecting shell metacharacters into environment variables used in OpenClaw scheduled task scripts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Mar 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-pj5x-38rw-6fph, MINI-7wx6-987j-4q5v, MINI-g4q2-h2qj-2gc6

## What is CVE-2026-22176?

CVE-2026-22176 is a medium-severity command injection vulnerability in Openclaw Openclaw, published on 19 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenClaw versions prior to 2026.2.19 contain a command injection vulnerability in Windows Scheduled Task script generation where environment variables are written to gateway.cmd using unquoted set KEY=VALUE assignments, allowing shell metacharacters to break out of assignment context. Attackers can inject arbitrary commands through environment variable values containing metacharacters like &, |, ^, %, or ! to achieve command execution when the scheduled task script is generated and executed.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

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.19 |
| `openclaw` | npm | All versions | 2026.2.19 |

Products: Openclaw Openclaw.

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

Upgrade openclaw to 2026.2.19 or later.

## Is CVE-2026-22176 being exploited?

There is no known exploitation of CVE-2026-22176 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-22176 and fix it if it is affected.

What it is: CVE-2026-22176 is a medium-severity command injection vulnerability in Openclaw Openclaw, published on 19 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22176 in the wild and no public exploit code.

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

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-22176/ (Markdown: https://insights.sbomify.com/CVE-2026-22176/index.md)
```

## Sources

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

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