Openclaw CVE-2026-32067

While the CVSS score of 3.7 is relatively low, the risk assessment requires multi-signal analysis. The CVSS vector (AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N) indicates the vulnerability requires network access, high attack complexity, low privileges, and user interaction, which limits exploitability in automated scenarios. However, the authorization bypass nature (CWE-863) combined with the multi-account context means that in deployments with shared pairing workflows or federated account systems, motivated insiders or account-compromised users could systematically escalate privileges across account boundaries with minimal effort once initial access is gained. The lack of KEV designation and unknown EPSS score suggest this is not a high-priority zero-day or widely exploited vulnerability in the wild. The availability of vendor patches and the moderate technical impact (confidentiality and integrity only, no availability impact) further reduce acute risk. Real-world priority depends on deployment model: organizations using OpenClaw's multi-account features with sensitive inter-account DM policies should patch promptly; single-account or air-gapped deployments face lower risk.

An attacker with low privileges gains access to Account A (perhaps via credential compromise or as a legitimate user) and requests to be approved as a direct message sender. An administrator approves this pairing in Account A. Due to the authorization bypass flaw, the attacker is then automatically accepted as an approved sender in Account B (and potentially other accounts) without any additional approval step or user interaction beyond what was already granted for Account A. The attacker can now send direct messages to users in Account B under the guise of an approved sender, potentially exfiltrating sensitive data or conducting social engineering attacks across organizational boundaries. The high attack complexity (AC:H) and required user interaction (UI:R) suggest this scenario typically requires initial account compromise or social engineering to gain the PR:L foothold, but once established, the cross-account escalation path is deterministic and requires no additional interaction.