# CVE-2026-100559: OpenClaw before 2026.8.1 Command Injection via Escaped Newlines

> Attackers can execute arbitrary commands by bypassing allowlist validation using escaped newlines in OpenClaw.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-9f86-pvv5-rxfw, GHSA-w63f-m9c2-9g74, MINI-8vcp-m24g-m36v

## What is CVE-2026-100559?

CVE-2026-100559 is a high-severity command injection vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OpenClaw versions before 2026.8.1 contain a command parser vulnerability where escaped newlines confuse exec allowlist parsing, allowing hidden commands to execute. Attackers can craft input with escaped newlines to bypass allowlist validation and execute additional commands without expected authorization prompts.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-100559 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100559 is a high-severity command injection vulnerability in OpenClaw, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-100559 in the wild and no public exploit code.

Affected product: OpenClaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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