<?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-09-28T13:43:58.312658+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/bdu:2026-05042</id>
    <title>bdu:2026-05042</title>
    <updated>2026-09-28T13:43:58.319948+00:00</updated>
    <content>bdu:2026-05042</content>
    <link href="https://vulnerability.circl.lu/vuln/bdu:2026-05042"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-31999</id>
    <title>BREW-openclaw-cli-CVE-2026-31999 — CpenClaw's ACPX Windows wrapper shell fallback allowed cwd injection in specific paths</title>
    <updated>2026-09-28T13:43:58.320069+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>### Summary
On Windows ACPX paths, wrapper resolution for `.cmd`/`.bat` could fall back to shell execution in ways that allowed `cwd` influence to alter execution behavior.</p>
<p>### Impact
In affected Windows ACPX configurations, this could enable command execution integrity loss through cwd-influenced wrapper resolution.</p>
<p>### Fix
Wrapper resolution now prefers explicit PATH/PATHEXT entrypoint resolution and unwrapped Node/EXE execution, with strict fail-closed handling enabled by default for unresolvable wrapper cases.</p>
<p>### Affected and Patched Versions
- Affected: `&gt;= 2026.2.26, &lt; 2026.3.1`
- Patched: `2026.3.1`</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-31999"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-31999</id>
    <title>fkie_cve-2026-31999</title>
    <updated>2026-09-28T13:43:58.320178+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenClaw versions 2026.2.26 prior to 2026.3.1 on Windows contain a current working directory injection vulnerability in wrapper resolution for .cmd/.bat files that allows attackers to influence execution behavior through cwd manipulation. Remote attackers can exploit improper shell execution fallback mechanisms to achieve command execution integrity loss by controlling the current working directory during wrapper resolution.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-31999"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-6f6j-wx9w-ff4j</id>
    <title>GHSA-6f6j-wx9w-ff4j — CpenClaw's ACPX Windows wrapper shell fallback allowed cwd injection in specific paths</title>
    <updated>2026-09-28T13:43:58.320237+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 ACPX paths, wrapper resolution for `.cmd`/`.bat` could fall back to shell execution in ways that allowed `cwd` influence to alter execution behavior.</p>
<p>### Impact
In affected Windows ACPX configurations, this could enable command execution integrity loss through cwd-influenced wrapper resolution.</p>
<p>### Fix
Wrapper resolution now prefers explicit PATH/PATHEXT entrypoint resolution and unwrapped Node/EXE execution, with strict fail-closed handling enabled by default for unresolvable wrapper cases.</p>
<p>### Affected and Patched Versions
- Affected: `&gt;= 2026.2.26, &lt; 2026.3.1`
- Patched: `2026.3.1`</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-6f6j-wx9w-ff4j"/>
  </entry>
</feed>
