CVE-2026-27545: OpenClaw · Node system.run approval bypass via parent-symlink cwd rebind
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 2026.2.26 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.26
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 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 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.26.
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 patch is available in OpenClaw CLI version 2026.2.26 and later. Users should upgrade to this version once released. The fix includes immutable approval-time plan preparation and rejection of mutable parent symlink components to prevent bypass. If you cannot patch yet, users should be cautious about symlink usage in the cwd during node system.run executions.
Description
OpenClaw CLI versions up to 2026.2.25 contain a vulnerability where the approval context for node system.run executions can be bypassed by rebinding a writable parent symlink in the current working directory (cwd) after approval. This allows a command approved for one filesystem location to execute from a different location if the parent symlink changes between approval and execution. The issue is fixed in version 2026.2.26 by enforcing immutable approval-time plan preparation and rejecting mutable parent-symlink path components during approval-plan building.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-f7ww-2725-qvw2 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-27545 (opens in a new tab)
- github.com/openclaw/openclaw/commit/4b4718c8dfce2e2c48404aa5088af7c013bed60b (opens in a new tab)
- github.com/openclaw/openclaw/commit/4e690e09c746408b5e27617a20cb3fdc5190dbda (opens in a new tab)
- github.com/openclaw/openclaw/commit/78a7ff2d50fb3bcef351571cb5a0f21430a340c1 (opens in a new tab)
- github.com/openclaw/openclaw/commit/d06632ba45a8482192792c55d5ff0b2e21abb0a7 (opens in a new tab)
- github.com/openclaw/openclaw/commit/d82c042b09727a6148f3ca651b254c4a677aff26 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-approval-bypass-via-parent-symlink-current-working-directory-rebind (opens in a new tab)