What is the CVSS score of CVE-2026-32045?

CVE-2026-32045 has a CVSS 3.1 base score of 5.9 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.1%.

Which versions of Openclaw are affected by CVE-2026-32045?

CVE-2026-32045 presents moderate security risk rated CVSS 5.9. Exploitation could compromise the security of affected deployments. Proof-of-concept code is publicly available.. A patch is available.

Is there a public PoC exploit available for CVE-2026-32045?

Yes, a public proof-of-concept exploit is available for CVE-2026-32045. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-32045?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Vendor patch is available.

Openclaw CVE-2026-32045

EUVD-2026-13939 MEDIUM

Authentication Bypass by Spoofing (CWE-290)

2026-03-21 VulnCheck

Authentication Bypass Openclaw

5.9

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.9 MEDIUM

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

PoC Detected

Mar 24, 2026 - 21:16 vuln.today

Public exploit code

EUVD ID Assigned

Mar 21, 2026 - 01:00 euvd

EUVD-2026-13939

Analysis Generated

Mar 21, 2026 - 01:00 vuln.today

Patch released

Mar 21, 2026 - 01:00 nvd

Patch available

CVE Published

Mar 21, 2026 - 00:42 nvd

MEDIUM 5.9

DescriptionCVE.org

OpenClaw versions prior to 2026.2.21 incorrectly apply tokenless Tailscale header authentication to HTTP gateway routes, allowing bypass of token and password requirements. Attackers on trusted networks can exploit this misconfiguration to access HTTP gateway routes without proper authentication credentials.

AnalysisAI

OpenClaw versions prior to 2026.2.21 contain an authentication bypass vulnerability in HTTP gateway routes due to incorrect application of tokenless Tailscale header authentication. Attackers on trusted networks can access HTTP gateway routes without providing required token or password credentials, potentially exposing sensitive functionality. A patch is available from the vendor, and this vulnerability has been disclosed publicly via GitHub Security Advisory GHSA-hff7-ccv5-52f8.

Technical ContextAI

The vulnerability stems from a misconfiguration in how OpenClaw applies Tailscale header-based authentication mechanisms to HTTP gateway routes. Tailscale provides a zero-trust networking protocol that can authenticate users via HTTP headers, but OpenClaw incorrectly trusts these headers without validating accompanying token or password requirements. This is classified under CWE-290 (Authentication Bypass by Spoofing), which describes cases where authentication mechanisms can be bypassed by assuming trusted network positions. The affected product is identified via CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, indicating all versions prior to 2026.2.21 are vulnerable. The root cause is an authentication logic flaw rather than a cryptographic weakness, allowing an attacker already positioned on a trusted network to bypass secondary authentication controls.

RemediationAI

Upgrade OpenClaw immediately to version 2026.2.21 or later, which contains the authentication bypass fix. The patch is available via the vendor's GitHub repository at https://github.com/openclaw/openclaw/commit/356d61aacfa5b0f1d5830716ec59d70682a3e7b8. Until patching is completed, implement network-level mitigations by restricting HTTP gateway route access to specific trusted IP ranges using firewall rules or reverse proxy policies, disable Tailscale header-based authentication on HTTP gateway routes if not essential, and enable comprehensive logging and monitoring of all authentication attempts to HTTP gateway endpoints to detect suspicious access patterns. Verify the patch application by testing that HTTP gateway routes properly enforce token and password validation before granting access.