GHSA-xhq5-45pm-2gjr
## Summary Nextcloud Talk room authorization matched on collidable room names instead of the stable room token, allowing policy confusion across similarly named rooms. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: < 2026.3.22 - Fixed: >= 2026.3.22 - Latest released tag checked: `v2026.3.23-2` (`630f1479c44f78484dfa21bb407cbe6f171dac87`) - Latest published npm version checked: `2026.3.23-2` ## Fix Commit(s) - `a47722de7e3c9cbda8d5512747ca7e3bb8f6ee66` ## Release Status The fix shipped in `v2026.3.22` and remains present in `v2026.3.23` and `v2026.3.23-2`. ## 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. OpenClaw thanks @zpbrent for reporting.
Properties
- ghsa_id
- GHSA-xhq5-45pm-2gjr
- severity
- medium
- summary
- OpenClaw: Nextcloud Talk room allowlist matched colliding room names instead of stable room tokens
- cve_id
- GHSA-xhq5-45pm-2gjr
- is_ghsa_only
- true
- ghsa_published
- 2026-03-26T21:34:18Z
- source_url
- https://github.com/advisories/GHSA-xhq5-45pm-2gjr
- ghsa_updated
- 2026-03-26T21:34:18Z
Related Entities (4)
AFFECTS (1)
HAS_WEAKNESS (2)
REPORTED_BY (1)
Explore deeper with Ninja Signal's threat intelligence graph