<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T18:48:24.580778+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-31995</id>
    <title>CVE-2026-31995 — OpenClaw 2026.1.21 &lt; 2026.2.19 - Command Injection via Windows Shell Fallback in Lobster Extension</title>
    <updated>2026-10-02T18:48:24.585961+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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'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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31995"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-fg3m-vhrr-8gj6</id>
    <title>GHSA-fg3m-vhrr-8gj6 — OpenClaw has Windows Lobster shell fallback command injection in constrained fallback path</title>
    <updated>2026-10-02T18:48:24.586089+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-fg3m-vhrr-8gj6"/>
  </entry>
</feed>
