Which versions of OpenClaw are affected by CVE-2026-53810?

OpenClaw users face runtime code injection risks through the extension marketplace, exposing operator systems to malicious payloads if accounts with administrative marketplace privileges are…. A patch is available.

How to fix or mitigate CVE-2026-53810?

Within 24 hours: Identify all OpenClaw instances and confirm which versions are in production (vulnerable if before 2026.5.18). Within 7 days: Apply the vendor-released patch by upgrading to OpenClaw 2026.5.18 or later (security advisory GHSA-v6r2-jh58-xx6w). Within 30 days: Audit marketplace extension audit logs for any unauthorized changes and verify patch application across all deployments.

OpenClaw CVE-2026-53810

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

CVE-2026-53810 has a CVSS 4.0 base score of 7.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/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.0%.

EUVD-2026-36316 HIGH

Inclusion of Functionality from Untrusted Control Sphere (CWE-829)

2026-06-11 VulnCheck

GHSA-v6r2-jh58-xx6w

RCE Openclaw

7.7

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

7.7 HIGH

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

6.8 MEDIUM

Network-reachable marketplace but exploitation needs trusted operator privileges (PR:H) and a victim loading the extension (UI:R); full CIA impact on the runtime once loaded.

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

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

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

None

User Interaction

Scope

Lifecycle Timeline

Analysis Generated

Jun 11, 2026 - 21:25 vuln.today

DescriptionCVE.org

OpenClaw before 2026.5.18 contains a code execution vulnerability where marketplace runtime extension metadata can redirect loading toward unscanned package payloads. Attackers with trusted operator access can manipulate extension metadata to load plugin code outside reviewed package entry points, bypassing security scanning.

AnalysisAI

Arbitrary code execution in OpenClaw before 2026.5.18 allows operators with trusted marketplace access to redirect extension loading to unscanned package payloads, bypassing the platform's security scanning controls. The flaw stems from improper validation of runtime extension metadata (CWE-829), and while no public exploit has been identified at time of analysis, a vendor patch is available via GHSA-v6r2-jh58-xx6w and VulnCheck has tagged it as RCE.

Technical ContextAI

OpenClaw exposes a marketplace runtime that loads plugin extensions whose entry points are normally validated by an upstream security scan before publication. The vulnerability is a CWE-829 (Inclusion of Functionality from Untrusted Control Sphere) condition: the runtime trusts metadata fields that describe where to load plugin code from, but does not re-verify that the resolved load target is the same artifact that was scanned. By manipulating these metadata pointers, the loader can be steered to package payloads that never went through review, so the platform's scanning boundary stops being authoritative. The affected component is identified by CPE cpe:2.3:a:openclaw:openclaw:* and the CWE class is well-known for plugin/extension ecosystems where the manifest is trusted more than the bytes it points at.

RemediationAI

Vendor-released patch: upgrade OpenClaw to 2026.5.18 or later as described in GHSA-v6r2-jh58-xx6w (https://github.com/openclaw/openclaw/security/advisories/GHSA-v6r2-jh58-xx6w). Until the upgrade is rolled out, restrict the set of accounts holding trusted marketplace operator privileges and audit recent extension metadata changes for redirected load targets that point outside the scanned package entry points; this reduces the population of users that can stage the bypass but does not close the underlying loader behavior. Operators can also disable installation of new or updated marketplace extensions on production tenants until the patched build is deployed, accepting the trade-off that legitimate extension updates will be blocked, and review the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-arbitrary-code-execution-via-unscanned-marketplace-runtime-extension-metadata for any additional indicators.