Cyber Resilience

CVE-2026-32302

Openclaw ≤ 2026.3.11

Published
13 March 2026
Modified
24 March 2026
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2026-32302 is a high-severity Origin Validation Error (CWE-346) vulnerability in Openclaw Openclaw. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique DHCP Spoofing (T1557.003); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

This vulnerability is AI-related — categorised as LLM Application Platforms; in the Privacy and Disclosure risk domain.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-32302 is a vulnerability in OpenClaw, a personal AI assistant, affecting versions prior to 2026.3.11. It stems from inadequate origin validation for browser-originated WebSocket connections when the gateway.auth.mode is configured to trusted-proxy and requests include proxy headers. This allows connections from untrusted origins to bypass checks, inheriting authentication from a trusted reverse proxy and escalating to a privileged operator session. The issue is classified under CWE-346 (Origin Validation Error) with a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).

An attacker can exploit this vulnerability by tricking a user into visiting a malicious webpage from an untrusted origin, such as through phishing or social engineering, as it requires user interaction. The malicious page can then initiate a WebSocket connection routed through a trusted reverse proxy. If the proxy provides authentication headers, the connection inherits that identity without proper origin checks, granting the attacker high confidentiality and integrity impacts, including access to privileged operator functions in OpenClaw.

Mitigation is available in OpenClaw version 2026.3.11, which addresses the origin validation bypass. Security practitioners should upgrade to this release immediately. Relevant resources include the fixing commit at https://github.com/openclaw/openclaw/commit/ebed3bbde1a72a1aaa9b87b63b91e7c04a50036b, the release page at https://github.com/openclaw/openclaw/releases/tag/v2026.3.11, and the security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-5wcw-8jjv-m286.

As OpenClaw is a personal AI assistant, this vulnerability could expose sensitive AI-driven operations or data to unauthorized control, highlighting risks in AI system gateways with proxy-based authentication. No public evidence of real-world exploitation has been reported.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

OpenClaw is a personal AI assistant. Prior to 2026.3.11, browser-originated WebSocket connections could bypass origin validation when gateway.auth.mode was set to trusted-proxy and the request arrived with proxy headers. A page served from an untrusted origin could connect through a…

more

trusted reverse proxy, inherit proxy-authenticated identity, and establish a privileged operator session. This vulnerability is fixed in 2026.3.11.

CWE(s)

AI Security AnalysisAI

AI Category
LLM Application Platforms
Risk Domain
Privacy and Disclosure
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: ai

Related Threats

MITRE ATT&CK Enterprise Techniques

T1557.003 DHCP Spoofing Credential Access
Adversaries may redirect network traffic to adversary-owned systems by spoofing Dynamic Host Configuration Protocol (DHCP) traffic and acting as a malicious DHCP server on the victim network.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
T1557.001 Name Resolution Poisoning and SMB Relay Credential Access
By responding to LLMNR/NBT-NS/mDNS network traffic, adversaries may spoof an authoritative source for name resolution to force communication with an adversary controlled system.
T1557.002 ARP Cache Poisoning Credential Access
Adversaries may poison Address Resolution Protocol (ARP) caches to position themselves between the communication of two or more networked devices.
T1557.004 Evil Twin Credential Access
Adversaries may host seemingly genuine Wi-Fi access points to deceive users into connecting to malicious networks as a way of supporting follow-on behaviors such as [Network Sniffing](https://attack.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-41393Same product: Openclaw Openclaw
CVE-2026-41342Same product: Openclaw Openclaw
CVE-2026-41398Same product: Openclaw Openclaw
CVE-2026-41358Same product: Openclaw Openclaw
CVE-2026-41376Same product: Openclaw Openclaw
CVE-2026-27004Same product: Openclaw Openclaw
CVE-2026-24763Same product: Openclaw Openclaw
CVE-2026-25593Same product: Openclaw Openclaw
CVE-2026-24764Same product: Openclaw Openclaw
CVE-2026-35643Same product: Openclaw Openclaw

Affected Assets

openclaw
openclaw
≤ 2026.3.11

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement directly requires validating the source of data before allowing transmission or receipt.

Device identification and authentication mandates verifying the source before establishing connections.

Session authenticity mechanisms require validation that communications originate from the expected party.

Boundary protection at interfaces enforces checks on the origin of incoming communications.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

Authentication directly verifies the source of users/services/hardware, mitigating origin validation failures.

PR.AA-04 mostly match
prevents

Verifying identity assertions enforces origin validation for conveyed claims.

ID.AM-03 partial match
prevents

Documenting authorized flows supports origin validation by defining expected sources.

PR.IR-01 partial match
prevents

Protecting networks from unauthorized access requires origin checks on communication sources.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

Network security controls enforce origin validation at network boundaries.

mitigates

Security of network services includes validating the authenticity of service endpoints.

mitigates

Network segregation reduces exposure but does not directly validate origins.

prevents

Application security requirements explicitly call for origin validation of inputs and communications.

prevents

Secure architecture principles encourage origin checks but do not mandate them.

prevents

Secure coding practices include implementing proper origin validation to prevent spoofing.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (3 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-346
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-346
  • V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-346

References