Is there a patch available for CVE-2026-42429?

Yes, a patch is available for CVE-2026-42429. Update the affected software to the latest version immediately.

OpenClaw CVE-2026-42429

Q: What is the CVSS score of CVE-2026-42429?

CVE-2026-42429 has a CVSS 4.0 base score of 6.0 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

EUVD-2026-26131 MEDIUM

Incorrect Authorization (CWE-863)

2026-04-28 VulnCheck

Authentication Bypass Privilege Escalation Openclaw

6.0

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

6.0 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.1 HIGH

Network-reachable via gateway HTTP; PR:L because operator.read credentials required; S:U per single-user trust model; I:H for unauthorized write access; C:L for incidental read exposure.

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

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 04:14 vuln.today

Analysis Generated

Jul 24, 2026 - 04:14 vuln.today

Severity Changed

Apr 28, 2026 - 19:52 NVD

HIGH MEDIUM

CVSS changed

Apr 28, 2026 - 19:52 NVD

7.1 (HIGH) 6.0 (MEDIUM)

EUVD ID Assigned

Apr 28, 2026 - 19:30 euvd

EUVD-2026-26131

Patch released

Apr 28, 2026 - 19:30 nvd

Patch available

CVE Published

Apr 28, 2026 - 18:10 nvd

MEDIUM 6.0

DescriptionCVE.org

OpenClaw before 2026.4.8 contains a privilege escalation vulnerability in the gateway plugin HTTP authentication mechanism that widens identity-bearing operator.read requests into runtime operator.write permissions. Attackers can exploit this by sending read-scoped requests through the gateway auth route to gain unauthorized write access to runtime operations.

AnalysisAI

Privilege escalation in OpenClaw's gateway plugin HTTP authentication mechanism allows an authenticated user with operator.read scope to gain unauthorized operator.write runtime access. The gateway auth route incorrectly widens identity-bearing read-scoped requests into write permissions, bypassing the intended authorization boundary. No active exploitation has been identified (CISA KEV absent), and the vendor has confirmed a patch in version 2026.4.8 of the npm package.

Technical ContextAI

OpenClaw (npm package openclaw, CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) is a user-controlled local AI assistant. The vulnerability resides in the gateway plugin's HTTP authentication path (auth: gateway), which is responsible for mediating identity and permission scopes between upstream trusted-proxy requests and runtime plugin routes. CWE-863 (Incorrect Authorization) identifies the root cause: the authorization logic fails to enforce scope boundaries, allowing an operator.read credential to be silently elevated to operator.write by the gateway auth handler. Because OpenClaw operates under a single-user trust model rather than a multi-tenant service boundary, the practical blast radius is constrained to the local operator context, but the scope widening still undermines the principle of least privilege within that boundary.

RemediationAI

Upgrade the openclaw npm package to version 2026.4.8 or later, which contains the vendor-confirmed patch (commit d7c3210cd6f5fdfdc1beff4c9541673e814354d5). The fix is documented in the GitHub Security Advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-4f8g-77mw-3rxc and the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-privilege-escalation-via-gateway-plugin-http-authentication. If immediate upgrade is not possible and the gateway plugin is in use, disabling the auth: gateway HTTP authentication mode on plugin routes would eliminate the vulnerable code path, at the cost of losing gateway-mediated authentication for those routes. No other confirmed workarounds are documented by the vendor.