How severe is GHSA-vffc-f7r7-rx2w?

No CVSS score has been assigned to GHSA-vffc-f7r7-rx2w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vffc-f7r7-rx2w?

GHSA-vffc-f7r7-rx2w affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-vffc-f7r7-rx2w?

Update openclaw to 2026.2.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vffc-f7r7-rx2w is resolved across your whole dependency graph.

How do I detect GHSA-vffc-f7r7-rx2w in my npm dependencies?

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.

How do I mitigate GHSA-vffc-f7r7-rx2w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-vffc-f7r7-rx2w?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vffc-f7r7-rx2w can be triaged on real exposure rather than presence alone.

Is GHSA-vffc-f7r7-rx2w actively exploited in the wild?

No public exploit code has been indexed for GHSA-vffc-f7r7-rx2w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vffc-f7r7-rx2w?

GHSA-vffc-f7r7-rx2w has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vffc-f7r7-rx2w?

GHSA-vffc-f7r7-rx2w is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vffc-f7r7-rx2w published, and has it been updated?

GHSA-vffc-f7r7-rx2w was published on March 3, 2026 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-vffc-f7r7-rx2w — openclaw

Fix: openclaw/openclaw@61f646c

GHSA-vffc-f7r7-rx2w is a CWE-77 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw Improperly Neutralizes Line Breaks in systemd Unit Generation Enables Local Command Execution (Linux)

Also known asCVE-2026-32063

Published

Mar 3, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-vffc-f7r7-rx2w.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

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.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.7Mdownloads / week

Description

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, \\s is 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.ts
src/commands/daemon-install-helpers.ts
src/config/env-vars.ts
src/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.vars and trigger install/reinstall.

Fix Commit(s)

61f646c41fb43cd87ed48f9125b4718a30d38e84

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.21`npm install openclaw@2026.2.21`

Detection & mitigation playbook

Open-source dependency

Detect
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 GHSA-vffc-f7r7-rx2w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vffc-f7r7-rx2w can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vffc-f7r7-rx2w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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/

O3 Security · Impact-Aware SCA

Is GHSA-vffc-f7r7-rx2w in your dependencies?

O3 Security finds GHSA-vffc-f7r7-rx2w across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works