https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 14:12:08 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32895 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions prior to 2026.2.26 fail to enforce sender authorization in member and message subtype system event handlers, allowing unauthorized events to be enqueued. Attackers can bypass Slack DM allowlists and per-channel user allowlists by sending system events from non-allowlisted senders through message_changed, message_deleted, and thread_broadcast events.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions prior to 2026.2.26 fail to enforce sender authorization in member and message subtype system event handlers, allowing unauthorized events to be enqueued. Attackers can bypass Slack DM allowlists and per-channel user allowlists by sending system events from non-allowlisted senders through message_changed, message_deleted, and thread_broadcast events.</p> https://vulnerability.circl.lu/vuln/cve-2026-32895 https://vulnerability.circl.lu/vuln/ghsa-v8cg-4474-49v8 <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary Slack `member_*` and `message` subtype system events (`message_changed`, `message_deleted`, `thread_broadcast`) were not consistently enforcing sender authorization before enqueueing system events.</p> <p>### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version: `2026.2.25` - Affected range: `&lt;= 2026.2.25` - Planned patched version: `2026.2.26` (pre-set for publish-readiness)</p> <p>### Technical Details Slack system-event handlers in `src/slack/monitor/events/members.ts` and `src/slack/monitor/events/messages.ts` enqueued events after channel checks without shared sender authorization. Deployments relying on Slack DM allowlists (`dmPolicy` / `allowFrom`) or per-channel `users` allowlists could receive unauthorized system-event ingress from non-allowlisted senders.</p> <p>The fix routes those handlers through `authorizeAndResolveSlackSystemEventContext(...)` and fails closed when message subtype sender identity cannot be resolved.</p> <p>### Fix Commit(s) - `3d30ba18a2aba1e1b302e77ff33145c3b06c01c8`</p> <p>### Release Process Note `patched_versions` is pre-set to `&gt;= 2026.2.26` so once npm `2026.2.26` is published, this advisory can be published without further field edits.</p> <p>Thanks @tdjackey for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary Slack `member_*` and `message` subtype system events (`message_changed`, `message_deleted`, `thread_broadcast`) were not consistently enforcing sender authorization before enqueueing system events.</p> <p>### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version: `2026.2.25` - Affected range: `&lt;= 2026.2.25` - Planned patched version: `2026.2.26` (pre-set for publish-readiness)</p> <p>### Technical Details Slack system-event handlers in `src/slack/monitor/events/members.ts` and `src/slack/monitor/events/messages.ts` enqueued events after channel checks without shared sender authorization. Deployments relying on Slack DM allowlists (`dmPolicy` / `allowFrom`) or per-channel `users` allowlists could receive unauthorized system-event ingress from non-allowlisted senders.</p> <p>The fix routes those handlers through `authorizeAndResolveSlackSystemEventContext(...)` and fails closed when message subtype sender identity cannot be resolved.</p> <p>### Fix Commit(s) - `3d30ba18a2aba1e1b302e77ff33145c3b06c01c8`</p> <p>### Release Process Note `patched_versions` is pre-set to `&gt;= 2026.2.26` so once npm `2026.2.26` is published, this advisory can be published without further field edits.</p> <p>Thanks @tdjackey for reporting.</p> https://vulnerability.circl.lu/vuln/ghsa-v8cg-4474-49v8