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

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

OpenClaw CVE-2026-62219

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

CVE-2026-62219 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.2%.

Q: Which versions of OpenClaw are affected by CVE-2026-62219?

Authorization bypass in OpenClaw's hooks `allowedAgentIds` validation allows a lower-trust authenticated caller to circumvent agent ID restrictions by submitting blank agent IDs, effectively…. A patch is available.

EUVD-2026-45107 MEDIUM

Incorrect Authorization (CWE-863)

2026-07-17 VulnCheck

GHSA-jx9m-6q5c-jrgm

Authentication Bypass Openclaw

6.0

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) 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

5.9 MEDIUM

Network vector but AC:H reflects the AT:P attack requirement; PR:L for required low-trust authentication; integrity high for unauthorized action execution; no availability impact.

3.1 AV:N/AC:H/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 Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 17, 2026 - 02:32 EUVD

Analysis Generated

Jul 17, 2026 - 01:04 vuln.today

DescriptionCVE.org

OpenClaw 2026.2.12 before 2026.5.26 contain an authorization bypass vulnerability in the hooks allowedAgentIds validation. A lower-trust caller or configured input path can bypass agent ID restrictions by submitting blank agent IDs, allowing actions that should require stronger authorization or policy checks.

AnalysisAI

Authorization bypass in OpenClaw's hooks allowedAgentIds validation allows a lower-trust authenticated caller to circumvent agent ID restrictions by submitting blank agent IDs, effectively elevating privileges to perform actions gated behind stronger policy controls. Affected versions span OpenClaw 2026.2.12 through versions prior to 2026.5.26, with the flaw traceable to improper input validation of the agent identifier field during hook processing. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog, though the high integrity impact (VI:H per CVSS 4.0) signals meaningful risk to deployments that rely on agent-scoped authorization boundaries.

Technical ContextAI

CWE-863 (Incorrect Authorization) describes the root cause: the system performs an authorization check but the logic fails when the input is blank or empty, treating a null/empty agent ID as passing validation rather than failing closed. OpenClaw's hooks mechanism uses an allowedAgentIds list to restrict which agents may trigger certain actions; the bypass occurs because the validation routine does not explicitly reject blank identifiers before evaluating them against the allowlist. The affected CPE is cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, covering all OpenClaw application builds from 2026.2.12 up to (not including) 2026.5.26. The 'configured input path' language in the description suggests the vulnerability surface is specifically within the hooks subsystem and may require a caller operating within a particular integration context.

RemediationAI

The primary fix is to upgrade to OpenClaw 2026.5.26 or later, which resolves the blank agent ID bypass in the hooks allowedAgentIds validation. The vendor advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-724r-v4wf-mqc5 and the VulnCheck analysis at https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-blank-agent-ids should be consulted for confirmation of the patched release. If immediate upgrade is not possible, operators should consider restricting access to the hooks endpoint to only fully trusted callers at the network or application-gateway layer, accepting the trade-off that this may break legitimate lower-trust integration paths. Additionally, reviewing and tightening the trust model for callers that interact with hooks - ensuring no lower-trust path can reach the allowedAgentIds validation layer with attacker-controlled input - would reduce exposure without a full upgrade.