<?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-03T05:18:33.889285+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-41358</id>
    <title>BREW-openclaw-cli-CVE-2026-41358 — OpenClaw: Slack thread context could include messages from non-allowlisted senders</title>
    <updated>2026-10-03T05:18:33.955881+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Summary</p>
<p>Before OpenClaw 2026.4.2, Slack thread starter and thread-history context fetched through the API was not filtered by the effective sender allowlist. Messages from non-allowlisted senders could still enter the agent context when an allowlisted user replied in the same thread.</p>
<p>## Impact</p>
<p>A Slack deployment that relied on sender allowlists could still feed non-allowlisted thread content into the model context through thread history. This was a sender-access-control bypass on Slack thread context, not a direct channel-auth bypass.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected versions: `&lt;= 2026.4.1`
- Patched versions: `&gt;= 2026.4.2`
- Latest published npm version: `2026.4.1`</p>
<p>## Fix Commit(s)</p>
<p>- `ac5bc4fb37becc64a2ec314864cca1565e921f2d` — filter Slack thread context by the effective allowlist</p>
<p>## Release Process Note</p>
<p>The fix is present on `main` and is staged for OpenClaw `2026.4.2`. Publish this advisory after the `2026.4.2` npm release is live.</p>
<p>OpenClaw thanks @AntAISecurityLab for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-41358"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-292919</id>
    <title>EUVD-2026-292919</title>
    <updated>2026-10-03T05:18:33.955952+00:00</updated>
    <content>EUVD-2026-292919</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-292919"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41358</id>
    <title>fkie_cve-2026-41358</title>
    <updated>2026-10-03T05:18:33.955969+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenClaw before 2026.4.2 fails to filter Slack thread context by sender allowlist, allowing non-allowlisted messages to enter agent context. Attackers can inject unauthorized thread messages through allowlisted user replies to bypass sender access controls and manipulate model context.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-41358"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qm77-8qjp-4vcm</id>
    <title>GHSA-qm77-8qjp-4vcm — OpenClaw: Slack thread context could include messages from non-allowlisted senders</title>
    <updated>2026-10-03T05:18:33.955992+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Summary</p>
<p>Before OpenClaw 2026.4.2, Slack thread starter and thread-history context fetched through the API was not filtered by the effective sender allowlist. Messages from non-allowlisted senders could still enter the agent context when an allowlisted user replied in the same thread.</p>
<p>## Impact</p>
<p>A Slack deployment that relied on sender allowlists could still feed non-allowlisted thread content into the model context through thread history. This was a sender-access-control bypass on Slack thread context, not a direct channel-auth bypass.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected versions: `&lt;= 2026.4.1`
- Patched versions: `&gt;= 2026.4.2`
- Latest published npm version: `2026.4.1`</p>
<p>## Fix Commit(s)</p>
<p>- `ac5bc4fb37becc64a2ec314864cca1565e921f2d` — filter Slack thread context by the effective allowlist</p>
<p>## Release Process Note</p>
<p>The fix is present on `main` and is staged for OpenClaw `2026.4.2`. Publish this advisory after the `2026.4.2` npm release is live.</p>
<p>OpenClaw thanks @AntAISecurityLab for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qm77-8qjp-4vcm"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0980</id>
    <title>WID-SEC-W-2026-0980 — OpenClaw: Mehrere Schwachstellen</title>
    <updated>2026-10-03T05:18:33.956027+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Daten zu manipulieren, Sicherheitsmechanismen zu umgehen oder einen Denial-of-Service-Zustand zu erzeugen..</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0980"/>
  </entry>
</feed>
