<?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>Sun, 04 Oct 2026 19:57:44 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-32028 — OpenClaw: Discord DM reaction ingress missed dmPolicy/allowFrom checks in restricted setups</title>
      <link>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32028</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary
In OpenClaw `&amp;lt;= 2026.2.24`, Discord direct-message reaction notifications did not consistently apply the same DM authorization checks (`dmPolicy` / `allowFrom`) that are enforced for normal DM message ingress.&lt;/p&gt;
&lt;p&gt;In restrictive DM setups, a non-allowlisted Discord user who can react to a bot-authored DM message could still enqueue a reaction-derived system event in the session.&lt;/p&gt;
&lt;p&gt;This is a reaction-only ingress inconsistency. By itself it does not directly execute commands; practical impact depends on downstream automation/tool policy.&lt;/p&gt;
&lt;p&gt;### Details
The DM message path already enforces `dmPolicy`/`allowFrom` authorization, but the DM reaction-notification path previously allowed event enqueue under reaction mode checks without that same authorization gate.&lt;/p&gt;
&lt;p&gt;Fix in `main` aligns reaction ingress with normal message preflight for Discord DM/group-DM/guild policy boundaries and applies equivalent DM reaction authorization hardening for Slack to keep channel behavior consistent.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- `npm` package: `openclaw`
- Affected: `&amp;lt;= 2026.2.24`
- Patched: `&amp;gt;= 2026.2.25`&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the release (`2026.2.25`) so after npm release the advisory is published.&lt;/p&gt;
&lt;p&gt;Thanks @tdjackey 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;### Summary
In OpenClaw `&amp;lt;= 2026.2.24`, Discord direct-message reaction notifications did not consistently apply the same DM authorization checks (`dmPolicy` / `allowFrom`) that are enforced for normal DM message ingress.&lt;/p&gt;
&lt;p&gt;In restrictive DM setups, a non-allowlisted Discord user who can react to a bot-authored DM message could still enqueue a reaction-derived system event in the session.&lt;/p&gt;
&lt;p&gt;This is a reaction-only ingress inconsistency. By itself it does not directly execute commands; practical impact depends on downstream automation/tool policy.&lt;/p&gt;
&lt;p&gt;### Details
The DM message path already enforces `dmPolicy`/`allowFrom` authorization, but the DM reaction-notification path previously allowed event enqueue under reaction mode checks without that same authorization gate.&lt;/p&gt;
&lt;p&gt;Fix in `main` aligns reaction ingress with normal message preflight for Discord DM/group-DM/guild policy boundaries and applies equivalent DM reaction authorization hardening for Slack to keep channel behavior consistent.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- `npm` package: `openclaw`
- Affected: `&amp;lt;= 2026.2.24`
- Patched: `&amp;gt;= 2026.2.25`&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the release (`2026.2.25`) so after npm release the advisory is published.&lt;/p&gt;
&lt;p&gt;Thanks @tdjackey for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32028</guid>
    </item>
    <item>
      <title>cnvd-2026-14834</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2026-14834</link>
      <description>cnvd-2026-14834</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2026-14834</guid>
    </item>
    <item>
      <title>EUVD-2026-329424</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329424</link>
      <description>EUVD-2026-329424</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329424</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32028</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32028</link>
      <description>&lt;p&gt;OpenClaw versions prior to 2026.2.25 fail to enforce dmPolicy and allowFrom authorization checks on Discord direct-message reaction notifications, allowing non-allowlisted users to enqueue reaction-derived system events. Attackers can exploit this inconsistency by reacting to bot-authored DM messages to bypass DM authorization restrictions and trigger downstream automation or tool policies.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw versions prior to 2026.2.25 fail to enforce dmPolicy and allowFrom authorization checks on Discord direct-message reaction notifications, allowing non-allowlisted users to enqueue reaction-derived system events. Attackers can exploit this inconsistency by reacting to bot-authored DM messages to bypass DM authorization restrictions and trigger downstream automation or tool policies.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32028</guid>
    </item>
    <item>
      <title>GHSA-354r-7mfh-7rh2 — OpenClaw: Discord DM reaction ingress missed dmPolicy/allowFrom checks in restricted setups</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-354r-7mfh-7rh2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary
In OpenClaw `&amp;lt;= 2026.2.24`, Discord direct-message reaction notifications did not consistently apply the same DM authorization checks (`dmPolicy` / `allowFrom`) that are enforced for normal DM message ingress.&lt;/p&gt;
&lt;p&gt;In restrictive DM setups, a non-allowlisted Discord user who can react to a bot-authored DM message could still enqueue a reaction-derived system event in the session.&lt;/p&gt;
&lt;p&gt;This is a reaction-only ingress inconsistency. By itself it does not directly execute commands; practical impact depends on downstream automation/tool policy.&lt;/p&gt;
&lt;p&gt;### Details
The DM message path already enforces `dmPolicy`/`allowFrom` authorization, but the DM reaction-notification path previously allowed event enqueue under reaction mode checks without that same authorization gate.&lt;/p&gt;
&lt;p&gt;Fix in `main` aligns reaction ingress with normal message preflight for Discord DM/group-DM/guild policy boundaries and applies equivalent DM reaction authorization hardening for Slack to keep channel behavior consistent.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- `npm` package: `openclaw`
- Affected: `&amp;lt;= 2026.2.24`
- Patched: `&amp;gt;= 2026.2.25`&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the release (`2026.2.25`) so after npm release the advisory is published.&lt;/p&gt;
&lt;p&gt;Thanks @tdjackey 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;### Summary
In OpenClaw `&amp;lt;= 2026.2.24`, Discord direct-message reaction notifications did not consistently apply the same DM authorization checks (`dmPolicy` / `allowFrom`) that are enforced for normal DM message ingress.&lt;/p&gt;
&lt;p&gt;In restrictive DM setups, a non-allowlisted Discord user who can react to a bot-authored DM message could still enqueue a reaction-derived system event in the session.&lt;/p&gt;
&lt;p&gt;This is a reaction-only ingress inconsistency. By itself it does not directly execute commands; practical impact depends on downstream automation/tool policy.&lt;/p&gt;
&lt;p&gt;### Details
The DM message path already enforces `dmPolicy`/`allowFrom` authorization, but the DM reaction-notification path previously allowed event enqueue under reaction mode checks without that same authorization gate.&lt;/p&gt;
&lt;p&gt;Fix in `main` aligns reaction ingress with normal message preflight for Discord DM/group-DM/guild policy boundaries and applies equivalent DM reaction authorization hardening for Slack to keep channel behavior consistent.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- `npm` package: `openclaw`
- Affected: `&amp;lt;= 2026.2.24`
- Patched: `&amp;gt;= 2026.2.25`&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`&lt;/p&gt;
&lt;p&gt;### Release Process Note
`patched_versions` is pre-set to the release (`2026.2.25`) so after npm release the advisory is published.&lt;/p&gt;
&lt;p&gt;Thanks @tdjackey for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-354r-7mfh-7rh2</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0542 — OpenClaw: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0542</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Dateien zu manipulieren, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Dateien zu manipulieren, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0542</guid>
    </item>
  </channel>
</rss>
