Skip to main content
VulnerabilityPublished Updated

CVE-2026-27545: OpenClaw · Node system.run approval bypass via parent-symlink cwd rebind

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 2026.2.26 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.2.26
Fixed in
  • 2026.2.26

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

Community reviews

Loading reviews…