# CVE-2026-27545: openclaw — Fixed in 2026.2.26

📦 npm

Not in CISA KEV

# CVE-2026-27545 — openclaw

[Fix: openclaw/openclaw@4b4718c](https://github.com/openclaw/openclaw/commit/4b4718c8dfce2e2c48404aa5088af7c013bed60b)

CVE-2026-27545 is a CWE-367 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw < 2026.2.26 - Approval Bypass via Parent Symlink Current Working Directory Rebind

Also known as[GHSA-f7ww-2725-qvw2](/vulnerability/GHSA-f7ww-2725-qvw2)

Published

Mar 18, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27545.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.1%probability of exploitation in next 30 days

Lower Risk+0.00%

Lower risk than most CVEs1th percentile — riskier than 1% of all scored CVEsHighest risk

0.00%0.21%0.43%0.64%0.0%0.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`openclaw`npm

2.5Mdownloads / week

## Description

### Summary

For `host=node` executions, approval context could be bypassed after approval-time by rebinding a writable parent symlink in `cwd` while preserving the visible `cwd` string.

### Affected Packages / Versions

-   Package: `openclaw` (npm)
-   Affected: `<= 2026.2.25`
-   Fixed: `>= 2026.2.26` (planned next npm release)

### Impact

A command approved for one filesystem location could execute from a different location if a mutable parent symlink changed between approval and execution.

### Fix

-   Added immutable approval-time plan preparation (`system.run.prepare`) and `systemRunPlanV2` canonical fields (`argv`, `cwd`, `agentId`, `sessionKey`).
-   Enforced canonical plan values through approval request storage and forwarding-time sanitization.
-   Rejected mutable parent-symlink path components during approval-plan building to block symlink rebind bypass.
-   Follow-up refactors centralized command catalogs and approval context/error handling to reduce future drift.

### Fix Commit(s)

-   `78a7ff2d50fb3bcef351571cb5a0f21430a340c1`
-   `d82c042b09727a6148f3ca651b254c4a677aff26`
-   `d06632ba45a8482192792c55d5ff0b2e21abb0a7`
-   `4e690e09c746408b5e27617a20cb3fdc5190dbda`
-   `4b4718c8dfce2e2c48404aa5088af7c013bed60b`

### Release Process Note

`patched_versions` is pre-set to the planned next release (`2026.2.26`). Once npm `openclaw@2026.2.26` is published, publish this advisory directly without further version-field edits.

OpenClaw thanks @tdjackey for reporting.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`openclaw` 

all versions

2026.2.26`npm install openclaw@2026.2.26`

## Affected Products

1 product · 1 configurations

Application

`openclaw`openclaw

< 2026.2.26

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update openclaw to 2026.2.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27545 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
    

## Frequently Asked Questions

\## Summary For \`host=node\` executions, approval context could be bypassed after approval-time by rebinding a writable parent symlink in \`cwd\` while preserving the visible \`cwd\` string. ## Affected Packages / Versions - Package: \`openclaw\` (npm) - Affected: \`<= 2026.2.25\` - Fixed: \`>= 2026.2.26\` (planned next npm release) ## Impact A command approved for one filesystem location could execute from a different location if a mutable parent symlink changed between approval and execution. ## Fix - Added immutable approval-time plan preparation (\`system.run.prepare\`) and \`systemRunPlanV2\` canonica

O3 Security · Impact-Aware SCA

### Is CVE-2026-27545 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)