https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 22:46:08 +0000 https://db.gcve.eu/vuln/cve-2026-32975 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.12 contains a weak authorization vulnerability in Zalouser allowlist mode that matches mutable group display names instead of stable group identifiers. Attackers can create groups with identical names to allowlisted groups to bypass channel authorization and route messages from unintended groups to the agent.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.12 contains a weak authorization vulnerability in Zalouser allowlist mode that matches mutable group display names instead of stable group identifiers. Attackers can create groups with identical names to allowlisted groups to bypass channel authorization and route messages from unintended groups to the agent.</p> https://db.gcve.eu/vuln/cve-2026-32975 https://db.gcve.eu/vuln/ghsa-f5mf-3r52-r83w <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>OpenClaw&#39;s Zalouser allowlist mode accepted mutable group names and normalized slugs as authorization matches instead of requiring stable group IDs. In deployments that used name-based `channels.zalouser.groups` entries together with permissive sender allowlists, a different group could be accepted by reusing the same display name as an allowlisted group.</p> <p>### Impact</p> <p>This weakened channel authorization for Zalouser group routing and could allow messages from an unintended group to reach the agent when operators relied on group names instead of stable IDs.</p> <p>### Affected versions</p> <p>`openclaw` `&lt;= 2026.3.11`</p> <p>### Patch</p> <p>Fixed in `openclaw` `2026.3.12`. Allowlist authorization now matches stable group identifiers, and users should update to `2026.3.12` or later.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>OpenClaw&#39;s Zalouser allowlist mode accepted mutable group names and normalized slugs as authorization matches instead of requiring stable group IDs. In deployments that used name-based `channels.zalouser.groups` entries together with permissive sender allowlists, a different group could be accepted by reusing the same display name as an allowlisted group.</p> <p>### Impact</p> <p>This weakened channel authorization for Zalouser group routing and could allow messages from an unintended group to reach the agent when operators relied on group names instead of stable IDs.</p> <p>### Affected versions</p> <p>`openclaw` `&lt;= 2026.3.11`</p> <p>### Patch</p> <p>Fixed in `openclaw` `2026.3.12`. Allowlist authorization now matches stable group identifiers, and users should update to `2026.3.12` or later.</p> https://db.gcve.eu/vuln/ghsa-f5mf-3r52-r83w