OpenClaw, packaged as the npm library 'openclaw', allows a caller to specify a different sender identifier in the message.action field. Because the system incorrectly trusts this identifier, an attacker with write scope can impersonate another user and trigger any channel action that would normally be denied. This is a classic authentication bypass (CWE‑639) that can lead to unauthorized operations and privilege escalation within the application.

The flaw affects installations of the OpenClaw package prior to version 2026.7.1 that run in identity‑bearing Gateway deployments, where authentication modes honor caller identity and apply narrow operator scopes.

The CVSS score of 7.2 classifies the vulnerability as high severity, and although the EPSS score is not available, the lack of a KEV listing does not diminish the threat. Attackers can exploit the flaw by sending a crafted request that includes a forged requester identity, a scenario that does not require elevated system access. The vendor has fixed the issue in 2026.7.1 and recommends restricting message.action to administrators and disabling sensitive channel actions that rely on requester identity to mitigate the risk until a patch is applied.