Openclaw CVE-2026-32057

The CVSS score of 5.9 reflects a moderate but non-negligible risk profile: the attack vector is network-based (AV:N), attack complexity is high (AC:H), and privileges are required (PR:L), indicating the attacker must already possess valid node role credentials. The vector notably shows high integrity impact (I:H) with no availability impact (A:N), meaning an attacker can modify or inject malicious node events rather than cause denial-of-service. The CVSS base score of 5.9 is somewhat conservative given the integrity impact; the AC:H constraint suggests the attack requires specific timing, state, or environmental conditions. However, the combination of authentication bypass (bypassing pairing) plus event execution capability creates a meaningful privilege escalation from node role to control-ui role. Without confirmed EPSS data, KEV status, or public POC availability provided in the intelligence, the real-world exploitation probability appears moderate; the attack requires pre-existing authentication and likely depends on implementation details or deployment configuration (reflected in the high AC rating). From an SSVC perspective, this vulnerability exhibits limited automatable exploitation (AC:H argues against trivial automation), but the technical impact is high (privilege escalation to full event control). Organizations with defense-in-depth controls (network segmentation, audit logging on websocket handlers, RBAC enforcement) may mitigate practical risk; however, the vulnerability should be treated as high-priority for OpenClaw deployments managing critical infrastructure or sensitive node operations.

An attacker with valid OpenClaw node role credentials (e.g., a compromised node service account or a disgruntled insider) establishes a websocket connection to the trusted-proxy and sends a client.id=control-ui identifier in the pairing handshake. Due to the lack of proper device identity verification, the proxy accepts the connection as a legitimate control-ui instance and grants authorization to execute node event flows. The attacker can then inject or trigger arbitrary node events—such as container deployments, data processing jobs, or privilege escalation scripts—without undergoing the intended control-ui pairing verification, effectively escalating from a passive node observer to an active event orchestrator. The high attack complexity (AC:H) suggests the attacker may need to craft the request at a specific time or exploit a race condition in the pairing logic, but once successful, the integrity impact is severe.