<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T10:31:08.830288+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32033</id>
    <title>BREW-openclaw-cli-CVE-2026-32033 — OpenClaw has a workspace-only sandbox guard mismatch for @-prefixed absolute paths</title>
    <updated>2026-10-08T10:31:08.834008+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>A workspace-only file-system guard mismatch allowed `@`-prefixed absolute paths to bypass boundary validation in some tool path checks.</p>
<p>### Impact
When `tools.fs.workspaceOnly=true`, certain `@`-prefixed absolute paths (for example `@/etc/passwd`) could be validated before canonicalization while runtime path handling normalized the prefix differently. In affected code paths this could permit reads outside the intended workspace boundary.</p>
<p>Per `SECURITY.md`, OpenClaw is primarily a personal-assistant runtime with trusted-user assumptions, and this path is gated behind non-default sandbox/tooling configuration. That reduces practical exposure, but the bypass is still a security bug and is fixed.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published at triage time: `2026.2.23`
- Affected versions: `&lt;= 2026.2.23`
- Patched versions: `&gt;= 2026.2.24`</p>
<p>### Fix Commit(s)
- `9ef0fc2ff8fa7b145d1e746d6eb030b1bf692260`</p>
<p>OpenClaw thanks @tdjackey for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32033"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2026-14848</id>
    <title>cnvd-2026-14848</title>
    <updated>2026-10-08T10:31:08.834084+00:00</updated>
    <content>cnvd-2026-14848</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2026-14848"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-329429</id>
    <title>EUVD-2026-329429</title>
    <updated>2026-10-08T10:31:08.834104+00:00</updated>
    <content>EUVD-2026-329429</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329429"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32033</id>
    <title>fkie_cve-2026-32033</title>
    <updated>2026-10-08T10:31:08.834116+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenClaw versions prior to 2026.2.24 contain a path traversal vulnerability where @-prefixed absolute paths bypass workspace-only file-system boundary validation due to canonicalization mismatch. Attackers can exploit this by crafting @-prefixed paths like @/etc/passwd to read files outside the intended workspace boundary when tools.fs.workspaceOnly is enabled.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-32033"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-27cr-4p5m-74rj</id>
    <title>GHSA-27cr-4p5m-74rj — OpenClaw has a workspace-only sandbox guard mismatch for @-prefixed absolute paths</title>
    <updated>2026-10-08T10:31:08.834138+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>A workspace-only file-system guard mismatch allowed `@`-prefixed absolute paths to bypass boundary validation in some tool path checks.</p>
<p>### Impact
When `tools.fs.workspaceOnly=true`, certain `@`-prefixed absolute paths (for example `@/etc/passwd`) could be validated before canonicalization while runtime path handling normalized the prefix differently. In affected code paths this could permit reads outside the intended workspace boundary.</p>
<p>Per `SECURITY.md`, OpenClaw is primarily a personal-assistant runtime with trusted-user assumptions, and this path is gated behind non-default sandbox/tooling configuration. That reduces practical exposure, but the bypass is still a security bug and is fixed.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published at triage time: `2026.2.23`
- Affected versions: `&lt;= 2026.2.23`
- Patched versions: `&gt;= 2026.2.24`</p>
<p>### Fix Commit(s)
- `9ef0fc2ff8fa7b145d1e746d6eb030b1bf692260`</p>
<p>OpenClaw thanks @tdjackey for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-27cr-4p5m-74rj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0501</id>
    <title>WID-SEC-W-2026-0501 — OpenClaw: Mehrere Schwachstellen</title>
    <updated>2026-10-08T10:31:08.834167+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen, vertrauliche Informationen offenzulegen oder andere nicht näher definierte Angriffe durchzuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0501"/>
  </entry>
</feed>
