https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 02:09:21 +0000 https://cve.radiocsirt.org/vuln/cve-2026-35624 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.22 contains a policy confusion vulnerability in room authorization that matches colliding room names instead of stable room tokens. Attackers can exploit similarly named rooms to bypass allowlist policies and gain unauthorized access to protected Nextcloud Talk rooms.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.22 contains a policy confusion vulnerability in room authorization that matches colliding room names instead of stable room tokens. Attackers can exploit similarly named rooms to bypass allowlist policies and gain unauthorized access to protected Nextcloud Talk rooms.</p> https://cve.radiocsirt.org/vuln/cve-2026-35624 https://cve.radiocsirt.org/vuln/ghsa-xhq5-45pm-2gjr <p><strong>Affected:</strong> npm: openclaw</p> <p>## Summary Nextcloud Talk room authorization matched on collidable room names instead of the stable room token, allowing policy confusion across similarly named rooms.</p> <p>## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: &lt; 2026.3.22 - Fixed: &gt;= 2026.3.22 - Latest released tag checked: `v2026.3.23-2` (`630f1479c44f78484dfa21bb407cbe6f171dac87`) - Latest published npm version checked: `2026.3.23-2`</p> <p>## Fix Commit(s) - `a47722de7e3c9cbda8d5512747ca7e3bb8f6ee66`</p> <p>## Release Status The fix shipped in `v2026.3.22` and remains present in `v2026.3.23` and `v2026.3.23-2`.</p> <p>## Code-Level Confirmation - extensions/nextcloud-talk/src/inbound.ts now resolves allowlist policy from roomToken-backed room identity. - extensions/nextcloud-talk/src/policy.ts now keys room authorization on stable room tokens instead of display names.</p> <p>OpenClaw thanks @zpbrent for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>## Summary Nextcloud Talk room authorization matched on collidable room names instead of the stable room token, allowing policy confusion across similarly named rooms.</p> <p>## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: &lt; 2026.3.22 - Fixed: &gt;= 2026.3.22 - Latest released tag checked: `v2026.3.23-2` (`630f1479c44f78484dfa21bb407cbe6f171dac87`) - Latest published npm version checked: `2026.3.23-2`</p> <p>## Fix Commit(s) - `a47722de7e3c9cbda8d5512747ca7e3bb8f6ee66`</p> <p>## Release Status The fix shipped in `v2026.3.22` and remains present in `v2026.3.23` and `v2026.3.23-2`.</p> <p>## Code-Level Confirmation - extensions/nextcloud-talk/src/inbound.ts now resolves allowlist policy from roomToken-backed room identity. - extensions/nextcloud-talk/src/policy.ts now keys room authorization on stable room tokens instead of display names.</p> <p>OpenClaw thanks @zpbrent for reporting.</p> https://cve.radiocsirt.org/vuln/ghsa-xhq5-45pm-2gjr