https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 11:38:53 +0000 https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-32923 <p><strong>Affected:</strong> Homebrew: openclaw-cli</p> <p>## Summary In affected versions of `openclaw`, Discord reaction ingestion for guild channels did not enforce the same member users and roles allowlist checks used for normal inbound guild messages. A non-allowlisted guild member could still trigger reaction events that were accepted and queued as trusted system events for the target session.</p> <p>## Impact This is an authorization bypass in the Discord allowlist path. Reaction text could be injected into downstream session context even when the reacting guild member was not permitted by the configured users or roles allowlist.</p> <p>## Affected Packages and Versions - Package: `openclaw` (npm) - Affected versions: `&lt; 2026.3.11` - Fixed in: `2026.3.11`</p> <p>## Technical Details The reaction ingress authorization path enforced DM, group, guild, and channel policy checks, but it did not apply the member-level users and roles allowlist gate that normal guild-message preflight uses. Accepted reactions were then enqueued as trusted system events for the routed session.</p> <p>## Fix OpenClaw now applies the same users and roles allowlist enforcement to guild reaction ingress that it already applies to normal inbound guild messages. The fix shipped in `openclaw@2026.3.11`.</p> <p>## Workarounds Upgrade to `2026.3.11` or later.</p> <p><strong>Affected:</strong> Homebrew: openclaw-cli</p> <p>## Summary In affected versions of `openclaw`, Discord reaction ingestion for guild channels did not enforce the same member users and roles allowlist checks used for normal inbound guild messages. A non-allowlisted guild member could still trigger reaction events that were accepted and queued as trusted system events for the target session.</p> <p>## Impact This is an authorization bypass in the Discord allowlist path. Reaction text could be injected into downstream session context even when the reacting guild member was not permitted by the configured users or roles allowlist.</p> <p>## Affected Packages and Versions - Package: `openclaw` (npm) - Affected versions: `&lt; 2026.3.11` - Fixed in: `2026.3.11`</p> <p>## Technical Details The reaction ingress authorization path enforced DM, group, guild, and channel policy checks, but it did not apply the member-level users and roles allowlist gate that normal guild-message preflight uses. Accepted reactions were then enqueued as trusted system events for the routed session.</p> <p>## Fix OpenClaw now applies the same users and roles allowlist enforcement to guild reaction ingress that it already applies to normal inbound guild messages. The fix shipped in `openclaw@2026.3.11`.</p> <p>## Workarounds Upgrade to `2026.3.11` or later.</p> https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-32923