How severe is GHSA-mqr9-vqhq-3jxw?

No CVSS score has been assigned to GHSA-mqr9-vqhq-3jxw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mqr9-vqhq-3jxw?

GHSA-mqr9-vqhq-3jxw affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-mqr9-vqhq-3jxw?

Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mqr9-vqhq-3jxw is resolved across your whole dependency graph.

How do I detect GHSA-mqr9-vqhq-3jxw in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mqr9-vqhq-3jxw 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-mqr9-vqhq-3jxw?

O3 pinpoints whether GHSA-mqr9-vqhq-3jxw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mqr9-vqhq-3jxw actively exploited in the wild?

No public exploit code has been indexed for GHSA-mqr9-vqhq-3jxw 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 type of vulnerability is GHSA-mqr9-vqhq-3jxw?

GHSA-mqr9-vqhq-3jxw is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-mqr9-vqhq-3jxw published, and has it been updated?

GHSA-mqr9-vqhq-3jxw was published on March 3, 2026 and was last updated on March 19, 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

GHSA-mqr9-vqhq-3jxw

Fix: openclaw/openclaw@280c6b1

GHSA-mqr9-vqhq-3jxw is a OS Command Injection vulnerability in openclaw. O3 Security confirms whether GHSA-mqr9-vqhq-3jxw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw Windows Scheduled Task script generation allowed local command injection via unsafe cmd argument handling

Also known asCVE-2026-31994

Published

Mar 3, 2026

Updated

Mar 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.1Mdownloads / week

Description

Summary

OpenClaw Windows Scheduled Task script generation allowed unsafe argument handling in generated gateway.cmd files. In vulnerable versions, cmd metacharacter-only values could be emitted without safe quoting/escaping, which could lead to unintended command execution when the scheduled task runs.

Details

The issue affected Windows daemon startup script generation in src/daemon/schtasks.ts.

Vulnerable behavior included:

Incomplete cmd argument quoting for metacharacter-only values.
Incomplete handling of cmd expansion-sensitive characters in script arguments.
Missing CR/LF guards for script-rendered fields.

The fix hardens Windows script generation by:

Separating schtasks argument quoting from batch script argument quoting.
Quoting cmd metacharacter arguments and escaping % / ! expansion cases.
Rejecting CR/LF in command arguments, task descriptions, and rendered environment assignments.
Adding regression tests for metacharacter and line-break injection paths.

Impact

This issue is local to Windows deployments and requires control over values that feed service script generation (for example install-time/runtime arguments or environment-derived values). It can result in unintended command execution in the scheduled task context.

Affected Packages / Versions

Package: openclaw (npm)
Vulnerable versions: <= 2026.2.17
Patched version: >= 2026.2.19 (planned next npm release)
Latest published npm version at update time (2026-02-19): 2026.2.17

Fix Commit(s)

280c6b117b2f0e24f398e5219048cd4cc3b82396

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.19

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mqr9-vqhq-3jxw 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 pinpoints whether GHSA-mqr9-vqhq-3jxw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mqr9-vqhq-3jxw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary OpenClaw Windows Scheduled Task script generation allowed unsafe argument handling in generated `gateway.cmd` files. In vulnerable versions, cmd metacharacter-only values could be emitted without safe quoting/escaping, which could lead to unintended command execution when the scheduled task runs. ### Details The issue affected Windows daemon startup script generation in `src/daemon/schtasks.ts`. Vulnerable behavior included: - Incomplete cmd argument quoting for metacharacter-only values. - Incomplete handling of cmd expansion-sensitive characters in script arguments. - Missing C

O3 Security · Impact-Aware SCA

Is GHSA-mqr9-vqhq-3jxw in your dependencies?

O3 detects GHSA-mqr9-vqhq-3jxw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works