https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 10:41:20 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32028 <p><strong>Affected:</strong> OpenClaw</p> <p>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.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-32028 https://vulnerability.circl.lu/vuln/ghsa-354r-7mfh-7rh2 <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary In OpenClaw `&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.</p> <p>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.</p> <p>This is a reaction-only ingress inconsistency. By itself it does not directly execute commands; practical impact depends on downstream automation/tool policy.</p> <p>### 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.</p> <p>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.</p> <p>### Affected Packages / Versions - `npm` package: `openclaw` - Affected: `&lt;= 2026.2.24` - Patched: `&gt;= 2026.2.25`</p> <p>### Fix Commit(s) - `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`</p> <p>### Release Process Note `patched_versions` is pre-set to the release (`2026.2.25`) so after npm release the advisory is published.</p> <p>Thanks @tdjackey for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary In OpenClaw `&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.</p> <p>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.</p> <p>This is a reaction-only ingress inconsistency. By itself it does not directly execute commands; practical impact depends on downstream automation/tool policy.</p> <p>### 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.</p> <p>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.</p> <p>### Affected Packages / Versions - `npm` package: `openclaw` - Affected: `&lt;= 2026.2.24` - Patched: `&gt;= 2026.2.25`</p> <p>### Fix Commit(s) - `aedf62ac7e669a89c7b299201bf6537dc6b12e0e`</p> <p>### Release Process Note `patched_versions` is pre-set to the release (`2026.2.25`) so after npm release the advisory is published.</p> <p>Thanks @tdjackey for reporting.</p> https://vulnerability.circl.lu/vuln/ghsa-354r-7mfh-7rh2