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

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

OpenClaw CVE-2026-62215

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

CVE-2026-62215 has a CVSS 4.0 base score of 5.1 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/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.2%.

EUVD-2026-45103 MEDIUM

Insufficient Verification of Data Authenticity (CWE-345)

2026-07-17 VulnCheck

GHSA-2x3r-854j-qm5f

Authentication Bypass Openclaw

5.1

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

5.1 MEDIUM

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/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

8.0 HIGH

Network vector with no privileges required; scope changed to capture high downstream C/I impact; UI:R and AC:H reflect the user interaction and complexity prerequisites from the 4.0 vector.

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

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Patch available

Jul 17, 2026 - 02:32 EUVD

Analysis Generated

Jul 17, 2026 - 01:05 vuln.today

DescriptionCVE.org

OpenClaw versions before 2026.6.5 contain an authentication bypass vulnerability in HTTP Canvas responses that allows lower-trust callers to forge trusted A2UI actions. Attackers can perform actions requiring stronger authorization by submitting crafted requests through configured input paths, bypassing intended policy checks.

AnalysisAI

Authentication bypass in OpenClaw before 2026.6.5 enables lower-trust network callers to forge A2UI actions that require higher authorization by submitting crafted HTTP Canvas responses through configured input paths. The flaw (CWE-345: Insufficient Verification of Data Authenticity) allows an attacker to subvert OpenClaw's trust hierarchy and execute privileged actions on downstream systems (SC:H/SI:H per CVSS 4.0), without any direct impact on the OpenClaw instance itself. No public exploit has been identified and the vulnerability is not in the CISA KEV catalog; the CVSS 4.0 score of 5.1 reflects significant real-world constraints from high attack complexity and required user interaction.

Technical ContextAI

OpenClaw (CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) implements an HTTP Canvas mechanism that carries response data between components, dispatching A2UI (application-to-UI) actions based on the trust level attributed to the originating caller. The root cause is CWE-345 (Insufficient Verification of Data Authenticity): the application does not adequately verify that A2UI actions embedded in HTTP Canvas responses genuinely originate from callers holding the requisite trust level. A lower-trust caller can therefore inject forged A2UI actions through configured input paths, and the system incorrectly treats those actions as having been produced by a higher-trust source. The scope change reflected in the CVSS 4.0 vector (VC:N/VI:N/VA:N with SC:H/SI:H) is consistent with this trust-relay architecture: the OpenClaw process itself is not directly compromised, but downstream systems that consume and honor the forged A2UI actions bear the High confidentiality and integrity impact.

RemediationAI

Upgrade to OpenClaw version 2026.6.5 or later, which is the first release addressing this authentication bypass; the 'before 2026.6.5' affected range in the CVE description identifies this as the remediated boundary. Consult the official vendor advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-vr7j-7684-7gm5 for release-specific patching instructions. If immediate upgrade is not feasible, consider restricting network access to the configured input paths that feed HTTP Canvas responses, limiting which callers can reach the affected endpoints at the network or application gateway layer - note that this may disrupt legitimate lower-trust caller workflows and must be tested. Additionally, enforcing strict allowlisting of trusted caller identities at the input path boundary could reduce exposure while the patch is staged, though this is an incomplete control given the nature of the trust-forging flaw.