<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 06:03:46 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-34506 — OpenClaw's MS Teams sender allowlist bypass when route allowlist is configured and sender allowlist is empty</title>
      <link>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-34506</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;OpenClaw&amp;#39;s Microsoft Teams plugin widened group sender authorization when a team/channel route allowlist was configured but `groupAllowFrom` was empty. Before the fix, a matching route allowlist entry could cause the message handler to synthesize wildcard sender authorization for that route, allowing any sender in the matched team/channel to bypass the intended `groupPolicy: &amp;#34;allowlist&amp;#34;` sender check.&lt;/p&gt;
&lt;p&gt;This does not affect default unauthenticated access, but it does weaken a documented Teams group authorization boundary and can allow unauthorized group senders to trigger replies in allowlisted Teams routes.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Latest published vulnerable version: `2026.3.7`
- Affected range: `&amp;lt;= 2026.3.7`
- Fixed in released version: `2026.3.8`&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)&lt;/p&gt;
&lt;p&gt;- `88aee9161e0e6d32e810a25711e32a808a1777b2`&lt;/p&gt;
&lt;p&gt;## Release Verification&lt;/p&gt;
&lt;p&gt;- Verified fixed in GitHub release `v2026.3.8` published on March 9, 2026.
- Verified `npm view openclaw version` resolves to `2026.3.8`.
- Verified the release contains the regression test covering the Teams route-allowlist sender-bypass case and that the test passes against the `v2026.3.8` tree.&lt;/p&gt;
&lt;p&gt;Thanks @zpbrent for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;OpenClaw&amp;#39;s Microsoft Teams plugin widened group sender authorization when a team/channel route allowlist was configured but `groupAllowFrom` was empty. Before the fix, a matching route allowlist entry could cause the message handler to synthesize wildcard sender authorization for that route, allowing any sender in the matched team/channel to bypass the intended `groupPolicy: &amp;#34;allowlist&amp;#34;` sender check.&lt;/p&gt;
&lt;p&gt;This does not affect default unauthenticated access, but it does weaken a documented Teams group authorization boundary and can allow unauthorized group senders to trigger replies in allowlisted Teams routes.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Latest published vulnerable version: `2026.3.7`
- Affected range: `&amp;lt;= 2026.3.7`
- Fixed in released version: `2026.3.8`&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)&lt;/p&gt;
&lt;p&gt;- `88aee9161e0e6d32e810a25711e32a808a1777b2`&lt;/p&gt;
&lt;p&gt;## Release Verification&lt;/p&gt;
&lt;p&gt;- Verified fixed in GitHub release `v2026.3.8` published on March 9, 2026.
- Verified `npm view openclaw version` resolves to `2026.3.8`.
- Verified the release contains the regression test covering the Teams route-allowlist sender-bypass case and that the test passes against the `v2026.3.8` tree.&lt;/p&gt;
&lt;p&gt;Thanks @zpbrent for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-34506</guid>
    </item>
    <item>
      <title>cnvd-2026-17897</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2026-17897</link>
      <description>cnvd-2026-17897</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2026-17897</guid>
    </item>
    <item>
      <title>EUVD-2026-329493</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329493</link>
      <description>EUVD-2026-329493</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329493</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34506</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34506</link>
      <description>&lt;p&gt;OpenClaw before 2026.3.8 contains a sender allowlist bypass vulnerability in its Microsoft Teams plugin that allows unauthorized senders to bypass intended authorization checks. When a team/channel route allowlist is configured with an empty groupAllowFrom parameter, the message handler synthesizes wildcard sender authorization, permitting any sender in the matched team/channel to trigger replies in allowlisted Teams routes.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw before 2026.3.8 contains a sender allowlist bypass vulnerability in its Microsoft Teams plugin that allows unauthorized senders to bypass intended authorization checks. When a team/channel route allowlist is configured with an empty groupAllowFrom parameter, the message handler synthesizes wildcard sender authorization, permitting any sender in the matched team/channel to trigger replies in allowlisted Teams routes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34506</guid>
    </item>
    <item>
      <title>GHSA-g7cr-9h7q-4qxq — OpenClaw's MS Teams sender allowlist bypass when route allowlist is configured and sender allowlist is empty</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g7cr-9h7q-4qxq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;OpenClaw&amp;#39;s Microsoft Teams plugin widened group sender authorization when a team/channel route allowlist was configured but `groupAllowFrom` was empty. Before the fix, a matching route allowlist entry could cause the message handler to synthesize wildcard sender authorization for that route, allowing any sender in the matched team/channel to bypass the intended `groupPolicy: &amp;#34;allowlist&amp;#34;` sender check.&lt;/p&gt;
&lt;p&gt;This does not affect default unauthenticated access, but it does weaken a documented Teams group authorization boundary and can allow unauthorized group senders to trigger replies in allowlisted Teams routes.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Latest published vulnerable version: `2026.3.7`
- Affected range: `&amp;lt;= 2026.3.7`
- Fixed in released version: `2026.3.8`&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)&lt;/p&gt;
&lt;p&gt;- `88aee9161e0e6d32e810a25711e32a808a1777b2`&lt;/p&gt;
&lt;p&gt;## Release Verification&lt;/p&gt;
&lt;p&gt;- Verified fixed in GitHub release `v2026.3.8` published on March 9, 2026.
- Verified `npm view openclaw version` resolves to `2026.3.8`.
- Verified the release contains the regression test covering the Teams route-allowlist sender-bypass case and that the test passes against the `v2026.3.8` tree.&lt;/p&gt;
&lt;p&gt;Thanks @zpbrent for reporting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;OpenClaw&amp;#39;s Microsoft Teams plugin widened group sender authorization when a team/channel route allowlist was configured but `groupAllowFrom` was empty. Before the fix, a matching route allowlist entry could cause the message handler to synthesize wildcard sender authorization for that route, allowing any sender in the matched team/channel to bypass the intended `groupPolicy: &amp;#34;allowlist&amp;#34;` sender check.&lt;/p&gt;
&lt;p&gt;This does not affect default unauthenticated access, but it does weaken a documented Teams group authorization boundary and can allow unauthorized group senders to trigger replies in allowlisted Teams routes.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Latest published vulnerable version: `2026.3.7`
- Affected range: `&amp;lt;= 2026.3.7`
- Fixed in released version: `2026.3.8`&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)&lt;/p&gt;
&lt;p&gt;- `88aee9161e0e6d32e810a25711e32a808a1777b2`&lt;/p&gt;
&lt;p&gt;## Release Verification&lt;/p&gt;
&lt;p&gt;- Verified fixed in GitHub release `v2026.3.8` published on March 9, 2026.
- Verified `npm view openclaw version` resolves to `2026.3.8`.
- Verified the release contains the regression test covering the Teams route-allowlist sender-bypass case and that the test passes against the `v2026.3.8` tree.&lt;/p&gt;
&lt;p&gt;Thanks @zpbrent for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g7cr-9h7q-4qxq</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0691 — OpenClaw: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0691</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder andere, nicht näher spezifizerte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder andere, nicht näher spezifizerte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0691</guid>
    </item>
  </channel>
</rss>
