Openclaw cli: OpenClaw vulnerable to arbitrary code execution via attacker-controlled setup-api.js loaded from cwd
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 8.4 High : upgrade to 2026.4.23 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.23
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 11 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.23.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in OpenClaw version 2026.4.23. Users should upgrade to this version or later to prevent arbitrary code execution via malicious setup-api.js files in the current working directory. The fix removes process.cwd() from the setup resolution fallback paths, ensuring only the canonical package root is trusted. No additional mitigation steps are required once the update is applied.
Description
OpenClaw CLI versions before 2026.4.23 contain a vulnerability where the bundled plugin setup resolver could execute arbitrary JavaScript from an attacker-controlled setup-api.js file located in the current working directory. This occurs when a user runs OpenClaw commands from a directory containing malicious setup files, leading to code execution under the user's privileges. The vulnerability requires user interaction and local access but does not depend on network exposure. The issue is fixed in version 2026.4.23 by restricting setup resolution to the canonical package root and excluding process.cwd().
References
- github.com/openclaw/openclaw/security/advisories/GHSA-r39h-4c2p-3jxp (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-45004 (opens in a new tab)
- github.com/openclaw/openclaw/commit/993781e6e6eaf50f033cfc3e3bf4f47059740707 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-arbitrary-code-execution-via-setup-api-js-in-current-working-directory (opens in a new tab)