OpenClaw versions before 2026.3.22 contain a policy confusion vulnerability in the room authorization logic. The software mistakenly resolves room identifiers based on colliding room names rather than stable room tokens. An attacker can create a room with a name that matches an existing protected room, causing the system to apply the unauthorized user’s permissions and bypass the configured allowlist. This allows unauthenticated or low‑privileged users to gain access to confidential Nextcloud Talk rooms.

The vulnerability affects the OpenClaw application across all environments that use the Node.js backend. Any deployment running a pre‑2026.3.22 release is impacted, as the issue is present in all prior versions. Administrators should verify the current patch level of OpenClaw in their environment and compare it to the 2026.3.22 release.

The CVSS score of 2.3 classifies the flaw as low severity, and no EPSS data or KEV listing is available. Based on the description, the likely attack vector involves remote submission of a room creation request, which is a typical HTTP API interaction. The exploitation requires knowledge of a protected room’s name and the ability to create a competing room. While the risk to individual deployments is low, the vulnerability can enable unauthorized access to sensitive communications. Monitoring for new advisories and applying the vendor patch remains the best mitigation.