Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain lower-trust caller access or write to configured plugin path
-
DeliveryPlant malicious workspace plugin
-
ExploitUser triggers setup-mode discovery
-
ExecutionOpenClaw loads untrusted plugin (CWE-829)
-
PersistPlugin code executes in app context
-
ImpactPersist actions beyond intended authorization
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Trusted source inclusion only
|
| Exploitation Conditions | Exploitation requires that OpenClaw's setup-mode discovery run against plugin/workspace input paths the attacker can influence, plus one of two footholds named in the advisory: 'lower-trust caller access' to the setup process, or 'control over configured input paths' where a malicious workspace plugin can be placed. Limiting factors from the CVSS 4.0 vector: the vector is local (AV:L), a specific attack precondition must be satisfied (AT:P), and a legitimate user must actively perform the triggering interaction (UI:A) - it cannot be driven remotely or fully unattended. This is therefore not remote unauthenticated exploitation against default configurations; it depends on the attacker's ability to control plugin sources and on setup mode being invoked. |
| Impact | The signals point to a real but access-gated issue rather than a mass-exploitable one. The CVSS 4.0 vector is AV:L (local, not network), AC:L, AT:P (a particular attack precondition must hold), PR:N, UI:A (active victim interaction required), with high confidentiality, integrity and availability impact to the vulnerable system (VC/VI/VA:H) and no subsequent-system impact (SC/SI/SA:N), yielding a base score of 7.1 (High). The description's own language - 'lower-trust caller access or control over configured input paths' - corroborates that some foothold or configuration influence is a prerequisite, consistent with AV:L and AT:P and slightly at odds with the PR:N metric, so the practical privilege requirement should be treated as 'some access likely needed' pending vendor clarification. No EPSS score, KEV listing, or POC was provided, so there is no evidence of active exploitation or automatable mass abuse; the 'Information Disclosure' tag understates the impact given the CVSS integrity/availability highs, which reflect code/action execution. Net: prioritize where OpenClaw processes attacker-influenceable workspace/config paths, but this is not an internet-facing wormable bug. |
| Exploit ScenarioDerived | An attacker who can write to a directory referenced by OpenClaw's configured plugin input paths (or who acts as a lower-trust caller into setup mode) plants a malicious workspace plugin. When a user triggers setup-mode discovery, OpenClaw loads the untrusted plugin and executes its logic with the application's authorization level, letting the attacker persist actions beyond their intended privileges. No public exploit code is identified, and the attack requires the local access, the specific precondition (AT:P), and the victim's active interaction (UI:A) reflected in the CVSS vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 17, 2026
Untrusted plugin loading in OpenClaw before 2026.5.22 lets an attacker with lower-trust caller access, or control over configured input paths, get malicious workspace plugins loaded through the setup-mode discovery process, executing or persisting actions above their intended authorization level. Exploitation is local and requires active user interaction plus a specific attack precondition (CVSS 4.0 base 7.1), and there is no public exploit identified at time of analysis. The root cause is inclusion of functionality from an untrusted control sphere (CWE-829) during setup-mode plugin discovery.
RemediationAI
Vendor-released patch: upgrade OpenClaw to 2026.5.22 or later, which is the primary and authoritative fix per GitHub advisory GHSA-rh6r-vvfc-86jq (https://github.com/openclaw/openclaw/security/advisories/GHSA-rh6r-vvfc-86jq). Until the upgrade is applied, reduce exposure by restricting who can influence the configured plugin input paths - store plugin/workspace directories on paths writable only by trusted administrators (removing group/other write permissions), and avoid pointing OpenClaw's configured input paths at shared, world-writable, or user-supplied locations, since this closes the 'control over configured input paths' vector at the cost of tighter path management. Where feasible, avoid running setup-mode discovery in contexts reachable by lower-trust callers, and validate that only vetted plugins are present before initiating setup; the trade-off is added operational friction when legitimately adding new plugins. Corroborating detail is available in the VulnCheck advisory (https://www.vulncheck.com/advisories/openclaw-untrusted-plugin-loading-via-setup-mode).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OpenClaw exposes a 'setup-mode discovery' mechanism that enumerates and loads workspace plugins from configured input paths. The flaw maps to CWE-829 (Inclusion of Functionality from an Untrusted Control Sphere): during setup, the discovery routine does not adequately validate the trust boundary of the plugin source, so code supplied by a lower-trust caller - or placed in a location the attacker can influence via configured input paths - is loaded and executed by the higher-trust OpenClaw process. Because plugins run as executable functionality inside the host application, loading an untrusted plugin is effectively arbitrary code/action execution within OpenClaw's authorization context. The single CPE provided, cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, covers all OpenClaw versions prior to the fix without narrowing to a platform or edition.
Know when Openclaw gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Local vector with a required precondition (AC:H) and attacker needing lower-trust caller access or path control (PR:L), victim must trigger setup (UI:R); loaded plugin executes with full C/I/A impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
OpenClaw before 2026.5.22 contain a vulnerability in setup-mode discovery that allows loading of untrusted workspace plugins. Attackers with lower-trust caller access or control over configured input paths can execute or persist actions beyond their intended authorization level.
Executive ViewAI
OpenClaw before version 2026.5.22 contains a local privilege escalation vulnerability (CVE-2026-62222) allowing lower-privileged users to load malicious plugins during setup-mode operations, enabling potential unauthorized actions and persistent system access. This vulnerability affects organizations where standard users interact with OpenClaw configuration interfaces. Immediate compensating controls are critical as no vendor patch is currently available.
No vendor-released patch identified at time of analysis. No public exploit identified at time of analysis. Interim mitigations: restrict plugin discovery to trusted, immutable directories; require administrative privileges for setup-mode access; enforce file system ACLs preventing lower-privileged user modification of plugin paths; disable plugin auto-discovery during normal operations; audit all currently loaded plugins for unauthorized additions; implement input validation on plugin path configurations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in OpenClaw Authorization Bypass and Policy Enforcement Flaws
View all 28Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.
Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b
OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att
An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.
OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e
Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in
Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a
Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach
OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director
OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func
OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste
OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low
EUVD-2026-45110
GHSA-7m8v-vm4p-2vf4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB