<?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-02T15:08:07.219498+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/brew-openclaw-cli-cve-2026-32061</id>
    <title>BREW-openclaw-cli-CVE-2026-32061 — OpenClaw vulnerable to arbitrary file read via $include directive</title>
    <updated>2026-10-02T15:08:08.824880+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Vulnerability</p>
<p>Path traversal in config `$include` resolution allowed arbitrary local file reads outside the config directory boundary (CWE-22).</p>
<p>### Attack Vectors</p>
<p>1. If an attacker can modify OpenClaw config, they can set `$include` to absolute paths (for example `/etc/passwd`) and read files accessible to the OpenClaw process.
2. If an attacker can modify OpenClaw config, they can use traversal paths (for example `../../...`) to escape the config directory.
3. If an attacker can create symlinks inside the config directory, they can point includes to external files unless real-path checks are enforced.
4. Impact scope is bounded by the file permissions of the OpenClaw runtime user; this is not an unauthenticated remote-only vector by itself.</p>
<p>## Impact</p>
<p>A successful exploit can expose local secrets and credentials readable by the OpenClaw process user, including API keys and private config material.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Vulnerable versions: `&lt;=2026.2.15`
- Patched versions: `&gt;=2026.2.17`</p>
<p>## Fix Commit(s)</p>
<p>- `d1c00dbb7c64a39e205464dae7f2a068420e91c1`</p>
<p>## Release Process Note</p>
<p>Patched version is pre-set to `2026.2.17`. Once npm release `2026.2.17` is available, this advisory is ready to publish.</p>
<p>OpenClaw thanks @aether-ai-agent for reporting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-32061"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-32061</id>
    <title>CVE-2026-32061 — OpenClaw &lt; 2026.2.17 - Arbitrary File Read via $include Directive Path Traversal</title>
    <updated>2026-10-02T15:08:08.824997+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openclaw</p>
<p>OpenClaw versions prior to 2026.2.17 contain a path traversal vulnerability in the $include directive resolution that allows reading arbitrary local files outside the config directory boundary. Attackers with config modification capabilities can exploit this by specifying absolute paths, traversal sequences, or symlinks to access sensitive files readable by the OpenClaw process user, including API keys and credentials.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-32061"/>
  </entry>
</feed>
