CyberRota Analysis
AI-GeneratedThe OpenClaw npm package prior to version 2026.7.1 is vulnerable to an authorization flaw that allows a write-scoped caller to spoof another user's identity during channel authorization checks. This could enable unauthorized actions based on the permissions of the impersonated user, potentially leading to significant security breaches depending on the channel and action involved. Organizations using OpenClaw in identity-sensitive deployments should prioritize upgrading to version 2026.7.1 or implementing workarounds to restrict sensitive actions to administrators.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
OpenClaw (npm package 'openclaw') before 2026.7.1 incorrectly trusts requester provenance in message.action. In identity-bearing Gateway deployments (authentication modes that honor caller identity and narrower operator scopes), a write-scoped caller can supply another sender's identifier to the channel authorization checks and invoke a channel action under that spoofed requester identity, reaching operations the channel adapter would have denied to the real caller. Practical impact depends on the enabled channel, the action, and the target account's permissions. Shared-secret token and password callers are full trusted operators under OpenClaw's security model and are out of scope. The issue is fixed in 2026.7.1; as a workaround, restrict message.action to administrators and disable sensitive channel actions that rely on requester identity.