CVE-2026-32063 — openclaw
Fix: openclaw/openclaw@61f646cCVE-2026-32063 is a CWE-77 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw 2026.2.19-2 < 2026.2.21 - Command Injection via Newline in systemd Unit Generation
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32063.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmDescription
Summary
A command injection vulnerability exists in OpenClaw’s Linux systemd unit generation path.
When rendering Environment= entries, attacker-controlled values are not rejected for CR/LF, and systemdEscapeArg() uses an incorrect whitespace-matching regex. This allows newline injection to break out of an Environment= line and inject standalone systemd directives (for example, ExecStartPre=). On service restart, the injected command is executed, resulting in local arbitrary command execution (local RCE) under the gateway service user.
Details
The issue is in src/daemon/systemd-unit.ts:
renderEnvLines(...)builds:Environment=${systemdEscapeArg(${key}=${value})}- No CR/LF validation is enforced for environment keys/values before writing unit lines.
systemdEscapeArg(...)uses:/[\\s"\\\\]/- In this regex,
\\sis interpreted as a literal backslash +s, not a whitespace character class. As a result, whitespace detection/quoting behavior is incorrect. Because systemd parses unit files line-by-line, a newline inside an environment value can inject an additional directive line. Example rendered output:
Environment=INJECT=ok
ExecStartPre=/bin/touch /tmp/oc15789_rce
At restart time, systemd executes ExecStartPre, enabling command execution.
Relevant code path/components involved in exploitation chain:
src/daemon/systemd-unit.tssrc/commands/daemon-install-helpers.tssrc/config/env-vars.tssrc/config/zod-schema.ts
Trigger conditions:
- Attacker can influence
config.env.vars(directly or indirectly). - Install/reinstall path is invoked to write/update the unit.
- Service restart occurs (
systemctl --user restart ...).
PoC
Environment: Linux host with systemd user services enabled.
- Configure a malicious environment value in OpenClaw config (
config.env.vars), including a newline and injected directive:
- Key:
INJECT - Value:
ok
ExecStartPre=/bin/touch /tmp/oc15789_rce
- Install/reinstall the gateway service (fixed port as requested):
openclaw gateway install --port 15789 --force
- Inspect the generated user unit file (default path):
~/.config/systemd/user/openclaw-gateway.service
Verify that an injected standalone line exists:
ExecStartPre=/bin/touch /tmp/oc15789_rce
- Reload and restart user service:
systemctl --user daemon-reload
systemctl --user restart openclaw-gateway.service
- Confirm command execution side effect:
ls -l /tmp/oc15789_rce
Impact
This is a local command execution vulnerability in OpenClaw’s systemd unit generation during install/reinstall flows.
- Type: Command injection via newline/directive injection in unit file generation.
- Execution context: Runs with the same privileges as the OpenClaw gateway service user.
- Affected users: Linux deployments using systemd user services where an attacker can control
config.env.varsand trigger install/reinstall.
Fix Commit(s)
61f646c41fb43cd87ed48f9125b4718a30d38e84
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.21npm install openclaw@2026.2.21 |
Affected Products
openclawopenclawDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32063 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2026-32063 in your dependencies?
Find it across npm, including transitive dependencies.