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

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

OpenClaw CVE-2026-53845

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

CVE-2026-53845 has a CVSS 4.0 base score of 2.3 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/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%.

EUVD-2026-37147 LOW

Protection Mechanism Failure (CWE-693)

2026-06-16 VulnCheck

GHSA-r7vv-6763-m739

GHSA-68xw-r643-9p5w

Authentication Bypass Openclaw

2.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

2.3 LOW

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/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

3.1 LOW

Network-reachable but requires targeting a specific dispatch path (AC:H); low-privilege authentication required (PR:L); integrity impact only, no confidentiality or availability effect.

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

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jun 16, 2026 - 20:02 EUVD

Analysis Generated

Jun 16, 2026 - 19:06 vuln.today

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on openclaw (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.5.6.

DescriptionCVE.org

OpenClaw before 2026.5.6 contains a hook bypass vulnerability where skill commands routed through the affected dispatch path skip before-tool-call hook coverage. Attackers can exploit this by sending skill commands through the vulnerable dispatch path to bypass hook-based auditing and policy enforcement mechanisms.

AnalysisAI

Hook-based policy enforcement bypass in OpenClaw before 2026.5.6 allows authenticated low-privilege network attackers to route skill commands through a specific vulnerable dispatch path, causing before-tool-call hooks to be skipped entirely. This silently circumvents audit logging and policy enforcement mechanisms that defenders rely on to detect and govern tool invocation behavior within the framework. No public exploit code has been identified at time of analysis, and CVSS 4.0 rates this at 2.3 (Low) with specific attack requirements (AT:P), limiting real-world risk primarily to environments that actively depend on hook-based security controls.

Technical ContextAI

OpenClaw is a tool and agent orchestration framework that routes skill commands through a dispatch path and invokes lifecycle hooks - specifically before-tool-call hooks - to apply policy enforcement and auditing prior to tool execution. The affected code path (CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) fails to invoke these hooks when skill commands traverse a specific alternative dispatch route, leaving hook coverage absent for that path. The root cause is classified as CWE-693 (Protection Mechanism Failure), meaning a security control exists in the product but can be rendered ineffective without the mechanism itself being compromised. This vulnerability does not grant direct data access or arbitrary code execution; it removes a defense-in-depth layer from tool invocations.

RemediationAI

Upgrade OpenClaw to version 2026.5.6 or later, which resolves the dispatch path flaw and ensures before-tool-call hooks are consistently invoked for all skill command routes. Consult the vendor security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-68xw-r643-9p5w for patch release confirmation and any additional guidance. If an immediate upgrade is not feasible, restrict access to the vulnerable dispatch path at the application or network layer so that only fully-vetted clients can issue skill commands - note this may disrupt legitimate workflows that depend on that path. As a compensating control, supplement OpenClaw hook-based auditing with out-of-band logging at the infrastructure level, such as reverse proxy access logs or network flow capture, so that tool invocations remain observable even if hooks are bypassed; this does not prevent the bypass but restores visibility.