OpenClaw: Nextcloud Talk room allowlist matched colliding room names instead of stable room tokens
## 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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-35624US | medium5.4OT elevated | — | ||
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 sim… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/openclaw/openclawPACKAGE
- https://github.com/openclaw/openclaw/commit/630f1479c44f78484dfa21bb407cbe6f171dac87WEB
- https://github.com/openclaw/openclaw/commit/a47722de7e3c9cbda8d5512747ca7e3bb8f6ee66WEB
- https://github.com/openclaw/openclaw/security/advisories/GHSA-xhq5-45pm-2gjrWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-35624ADVISORY
- https://www.vulncheck.com/advisories/openclaw-policy-confusion-via-room-name-collision-in-nextcloud-talkWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan