The vulnerability in OpenClaw versions before 2026.2.26 allows an attacker who is authorized as a sender in one account to be automatically approved as a sender in another account. This bypasses the intended direct message pairing policy and enables cross‑account access to direct message communication, potentially exposing sensitive information.

OpenClaw by OpenClaw, affecting all deployments of OpenClaw prior to the 2026.2.26 release. Any multi‑account deployment where direct message pairing approvals can be shared across accounts is vulnerable.

The CVSS score of 2 indicates low overall severity, and no EPSS data or KEV listing is available. The attack requires the attacker to have an existing sender approval in one account; from there the approval is silently accepted in another account. While the CVSS score is low, the potential for cross‑account privilege escalation could lead to data theft if sensitive DM payloads are accessed. Exploitation is likely only in environments that use shared pairing approvals across accounts rather than isolated per‑account approvals.