<?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-03T07:07:18.583653+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-42423</id>
    <title>BREW-openclaw-cli-CVE-2026-42423 — OpenClaw: strictInlineEval explicit-approval boundary bypassed by approval-timeout fallback on gateway and node exec ho…</title>
    <updated>2026-10-03T07:07:18.643909+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Impact</p>
<p>strictInlineEval explicit-approval boundary bypassed by approval-timeout fallback on gateway and node exec hosts.</p>
<p>The approval-timeout fallback could allow inline eval commands that strictInlineEval was meant to require explicit approval for.</p>
<p>OpenClaw is a user-controlled local assistant. This advisory is scoped to the OpenClaw trust model and does not assume a multi-tenant service boundary.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected versions: `&lt;=2026.4.2`
- Patched versions: `2026.4.8`</p>
<p>## Fix</p>
<p>The issue was fixed on `main` and is available in the patched npm version listed above. The verified fixed tree is commit `d7c3210cd6f5fdfdc1beff4c9541673e814354d5`.</p>
<p>## Verification</p>
<p>The fix was re-checked against `main` before publication, including targeted regression tests for the affected security boundary.</p>
<p>## Credits</p>
<p>Thanks @zsxsoft and @KeenSecurityLab for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-42423"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-308051</id>
    <title>EUVD-2026-308051</title>
    <updated>2026-10-03T07:07:18.643985+00:00</updated>
    <content>EUVD-2026-308051</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-308051"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42423</id>
    <title>fkie_cve-2026-42423</title>
    <updated>2026-10-03T07:07:18.644016+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenClaw before 2026.4.8 contains an approval-timeout fallback mechanism that bypasses strictInlineEval explicit-approval requirements on gateway and node exec hosts. Attackers can exploit this timeout fallback to execute inline eval commands that should require explicit user approval, circumventing the intended security boundary.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-42423"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-q2gc-xjqw-qp89</id>
    <title>GHSA-q2gc-xjqw-qp89 — OpenClaw: strictInlineEval explicit-approval boundary bypassed by approval-timeout fallback on gateway and node exec ho…</title>
    <updated>2026-10-03T07:07:18.644061+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Impact</p>
<p>strictInlineEval explicit-approval boundary bypassed by approval-timeout fallback on gateway and node exec hosts.</p>
<p>The approval-timeout fallback could allow inline eval commands that strictInlineEval was meant to require explicit approval for.</p>
<p>OpenClaw is a user-controlled local assistant. This advisory is scoped to the OpenClaw trust model and does not assume a multi-tenant service boundary.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected versions: `&lt;=2026.4.2`
- Patched versions: `2026.4.8`</p>
<p>## Fix</p>
<p>The issue was fixed on `main` and is available in the patched npm version listed above. The verified fixed tree is commit `d7c3210cd6f5fdfdc1beff4c9541673e814354d5`.</p>
<p>## Verification</p>
<p>The fix was re-checked against `main` before publication, including targeted regression tests for the affected security boundary.</p>
<p>## Credits</p>
<p>Thanks @zsxsoft and @KeenSecurityLab for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-q2gc-xjqw-qp89"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1005</id>
    <title>WID-SEC-W-2026-1005 — OpenClaw: Mehrere Schwachstellen</title>
    <updated>2026-10-03T07:07:18.644111+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um erweiterte Privilegien zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1005"/>
  </entry>
</feed>
