How severe is GHSA-f7ww-2725-qvw2?

No CVSS score has been assigned to GHSA-f7ww-2725-qvw2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f7ww-2725-qvw2?

GHSA-f7ww-2725-qvw2 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-f7ww-2725-qvw2?

Update openclaw to 2026.2.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f7ww-2725-qvw2 is resolved across your whole dependency graph.

How do I detect GHSA-f7ww-2725-qvw2 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-f7ww-2725-qvw2 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-f7ww-2725-qvw2?

O3 pinpoints whether GHSA-f7ww-2725-qvw2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-f7ww-2725-qvw2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f7ww-2725-qvw2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-f7ww-2725-qvw2?

GHSA-f7ww-2725-qvw2 is classified as CWE-367 (CWE-367). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f7ww-2725-qvw2 published, and has it been updated?

GHSA-f7ww-2725-qvw2 was published on March 2, 2026 and was last updated on March 18, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-f7ww-2725-qvw2

Fix: openclaw/openclaw@4b4718c

GHSA-f7ww-2725-qvw2 is a CWE-367 vulnerability in openclaw. O3 Security confirms whether GHSA-f7ww-2725-qvw2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Node system.run approval bypass via parent-symlink cwd rebind

Also known asCVE-2026-27545

Published

Mar 2, 2026

Updated

Mar 18, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.2Mdownloads / 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 [email protected] 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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f7ww-2725-qvw2 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-f7ww-2725-qvw2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f7ww-2725-qvw2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-f7ww-2725-qvw2 in your dependencies?

O3 detects GHSA-f7ww-2725-qvw2 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works