https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 23:46:44 +0000 https://cve.radiocsirt.org/vuln/cve-2026-32899 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions prior to 2026.2.25 fail to consistently apply sender-policy checks to reaction_* and pin_* non-message events before adding them to system-event context. Attackers can bypass configured DM policies and channel user allowlists to inject unauthorized reaction and pin events from restricted senders.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions prior to 2026.2.25 fail to consistently apply sender-policy checks to reaction_* and pin_* non-message events before adding them to system-event context. Attackers can bypass configured DM policies and channel user allowlists to inject unauthorized reaction and pin events from restricted senders.</p> https://cve.radiocsirt.org/vuln/cve-2026-32899 https://cve.radiocsirt.org/vuln/ghsa-rm2p-j3r7-4x4j <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary OpenClaw Slack monitor handled `reaction_*` and `pin_*` non-message events before applying sender-policy checks consistently.</p> <p>In affected versions, these events could be added to system-event context even when sender policy would not normally allow them.</p> <p>### Affected Packages / Versions - Package: npm `openclaw` - Latest published affected version confirmed: `2026.2.24` (npm latest as of February 26, 2026) - Affected range: `&lt;= 2026.2.24` - Patched version : `2026.2.25`</p> <p>### Technical Details - `reaction_*` and `pin_*` handlers now route through shared sender authorization (`authorizeSlackSystemEventSender`). - Enforced checks now include: - DM `dmPolicy` / `allowFrom` - channel `users` allowlist enforcement for non-DM channels - channel-level allow checks before system-event enqueue - Regression coverage added for DM allow/deny and channel-user allowlist deny paths.</p> <p>### Fix Commit(s) - `aedf62ac7e669a89c7b299201bf6537dc6b12e0e` - `75dfb71e4e8b7c2feba5a8ca662f92ea840e0147`</p> <p>### Impact Low-severity policy-consistency issue in Slack non-message event ingress. This may introduce unexpected reaction/pin context signals from senders outside configured policy.</p> <p>### Release Process Note `patched_versions` is pre-set to planned release `2026.2.25`. Advisory published with npm release `2026.2.25`.</p> <p>OpenClaw thanks @tdjackey for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary OpenClaw Slack monitor handled `reaction_*` and `pin_*` non-message events before applying sender-policy checks consistently.</p> <p>In affected versions, these events could be added to system-event context even when sender policy would not normally allow them.</p> <p>### Affected Packages / Versions - Package: npm `openclaw` - Latest published affected version confirmed: `2026.2.24` (npm latest as of February 26, 2026) - Affected range: `&lt;= 2026.2.24` - Patched version : `2026.2.25`</p> <p>### Technical Details - `reaction_*` and `pin_*` handlers now route through shared sender authorization (`authorizeSlackSystemEventSender`). - Enforced checks now include: - DM `dmPolicy` / `allowFrom` - channel `users` allowlist enforcement for non-DM channels - channel-level allow checks before system-event enqueue - Regression coverage added for DM allow/deny and channel-user allowlist deny paths.</p> <p>### Fix Commit(s) - `aedf62ac7e669a89c7b299201bf6537dc6b12e0e` - `75dfb71e4e8b7c2feba5a8ca662f92ea840e0147`</p> <p>### Impact Low-severity policy-consistency issue in Slack non-message event ingress. This may introduce unexpected reaction/pin context signals from senders outside configured policy.</p> <p>### Release Process Note `patched_versions` is pre-set to planned release `2026.2.25`. Advisory published with npm release `2026.2.25`.</p> <p>OpenClaw thanks @tdjackey for reporting.</p> https://cve.radiocsirt.org/vuln/ghsa-rm2p-j3r7-4x4j