https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 18:48:24 +0000 https://vulnerability.circl.lu/vuln/cve-2026-31995 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions 2026.1.21 prior to 2026.2.19 contain a command injection vulnerability in the Lobster extension&#39;s Windows shell fallback mechanism that allows attackers to inject arbitrary commands through tool-provided arguments. When spawn failures trigger shell fallback with shell: true, attackers can exploit cmd.exe command interpretation to execute malicious commands by controlling workflow arguments.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions 2026.1.21 prior to 2026.2.19 contain a command injection vulnerability in the Lobster extension&#39;s Windows shell fallback mechanism that allows attackers to inject arbitrary commands through tool-provided arguments. When spawn failures trigger shell fallback with shell: true, attackers can exploit cmd.exe command interpretation to execute malicious commands by controlling workflow arguments.</p> https://vulnerability.circl.lu/vuln/cve-2026-31995 https://vulnerability.circl.lu/vuln/ghsa-fg3m-vhrr-8gj6 <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary On Windows, the Lobster extension previously retried certain spawn failures (`ENOENT`/`EINVAL`) with `shell: true` for wrapper compatibility. In that fallback path, tool-provided arguments could be interpreted by `cmd.exe` if fallback was triggered.</p> <p>### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version at triage: `2026.2.17` - Affected range: `&gt;= 2026.1.21 &lt;= 2026.2.17` - Patched version: `2026.2.19` (pre-set for next release)</p> <p>### Fix The Windows shell fallback was removed. Wrapper compatibility is preserved by resolving `.cmd`/`.bat` shims to a concrete Node entrypoint (or executable) and executing with explicit argv (no shell). If a safe entrypoint cannot be resolved, execution now fails closed with a guided error.</p> <p>### Fix Commit(s) - `ba7be018da354ea9f803ed356d20464df0437916`</p> <p>### Severity Context This issue requires Windows plus fallback-triggering conditions, and argument control through a local operator-defined workflow.</p> <p>OpenClaw thanks @tdjackey for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary On Windows, the Lobster extension previously retried certain spawn failures (`ENOENT`/`EINVAL`) with `shell: true` for wrapper compatibility. In that fallback path, tool-provided arguments could be interpreted by `cmd.exe` if fallback was triggered.</p> <p>### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version at triage: `2026.2.17` - Affected range: `&gt;= 2026.1.21 &lt;= 2026.2.17` - Patched version: `2026.2.19` (pre-set for next release)</p> <p>### Fix The Windows shell fallback was removed. Wrapper compatibility is preserved by resolving `.cmd`/`.bat` shims to a concrete Node entrypoint (or executable) and executing with explicit argv (no shell). If a safe entrypoint cannot be resolved, execution now fails closed with a guided error.</p> <p>### Fix Commit(s) - `ba7be018da354ea9f803ed356d20464df0437916`</p> <p>### Severity Context This issue requires Windows plus fallback-triggering conditions, and argument control through a local operator-defined workflow.</p> <p>OpenClaw thanks @tdjackey for reporting.</p> https://vulnerability.circl.lu/vuln/ghsa-fg3m-vhrr-8gj6