Summary
OpenClaw Windows Scheduled Task script generation allowed local command injection via unsafe cmd argument handling
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.
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.
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 versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-31994? CVE-2026-31994 is a high-severity security vulnerability in openclaw (npm), affecting versions < 2026.2.19. It is fixed in 2026.2.19.
- Which versions of openclaw are affected by CVE-2026-31994? openclaw (npm) versions < 2026.2.19 is affected.
- Is there a fix for CVE-2026-31994? Yes. CVE-2026-31994 is fixed in 2026.2.19. Upgrade to this version or later.
- Is CVE-2026-31994 exploitable, and should I be worried? Whether CVE-2026-31994 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-31994 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-31994? Upgrade
openclawto 2026.2.19 or later.