What is GHSA-r5fq-947m-xm57?

## Summary In affected versions, when `apply_patch` was enabled and the agent ran without filesystem sandbox containment, crafted paths could cause file writes/deletes outside the configured workspace directory. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: ` = 2026.2.14` ## Details The non-sandbox path resolution in `apply_patch` did not enforce workspace containment. Inputs like `../../...` or absolute paths could escape the working directory in non-sandboxed mode. ## Impact Practical impact depends on deployment and who can trigger to

How severe is GHSA-r5fq-947m-xm57?

GHSA-r5fq-947m-xm57 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-r5fq-947m-xm57?

GHSA-r5fq-947m-xm57 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-r5fq-947m-xm57?

Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r5fq-947m-xm57 is resolved across your whole dependency graph.

How do I detect GHSA-r5fq-947m-xm57 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-r5fq-947m-xm57 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-r5fq-947m-xm57?

O3 pinpoints whether GHSA-r5fq-947m-xm57 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-r5fq-947m-xm57 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r5fq-947m-xm57 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 is the EPSS score for GHSA-r5fq-947m-xm57?

GHSA-r5fq-947m-xm57 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-r5fq-947m-xm57?

GHSA-r5fq-947m-xm57 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-r5fq-947m-xm57 published, and has it been updated?

GHSA-r5fq-947m-xm57 was published on February 19, 2026 and was last updated on March 13, 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-r5fq-947m-xm57

HIGH

OpenClaw has a path traversal in apply_patch could write/delete files outside the workspace

Also known asCVE-2026-32060

Published

Feb 19, 2026

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk50th percentile+0.11%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.4Mdownloads / week

Description

Summary

In affected versions, when apply_patch was enabled and the agent ran without filesystem sandbox containment, crafted paths could cause file writes/deletes outside the configured workspace directory.

Affected Packages / Versions

Package: openclaw (npm)
Affected: <= 2026.2.13
Fixed: >= 2026.2.14

Details

The non-sandbox path resolution in apply_patch did not enforce workspace containment. Inputs like ../../... or absolute paths could escape the working directory in non-sandboxed mode.

Impact

Practical impact depends on deployment and who can trigger tool execution. This is most relevant when tool invocation is exposed to less-trusted callers or when operators expected workspace-only containment.

Workarounds

Keep tools.exec.applyPatch.enabled disabled if you do not need apply_patch.
Keep tools.exec.applyPatch.workspaceOnly at its secure default of true.
Restrict who can trigger tool execution (and which tools are allowlisted).

Configuration Note

tools.exec.applyPatch.workspaceOnly: false intentionally opts out of workspace containment and can re-enable outside-workspace writes/deletes.

Fix

PR: https://github.com/openclaw/openclaw/pull/16405
Merge commit: 5544646a09c0121fca7d7093812dc2de8437c7f1

Credits

Thanks to @p80n-sec for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.14

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.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r5fq-947m-xm57 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-r5fq-947m-xm57 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-r5fq-947m-xm57. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary In affected versions, when `apply_patch` was enabled and the agent ran without filesystem sandbox containment, crafted paths could cause file writes/deletes outside the configured workspace directory. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `<= 2026.2.13` - Fixed: `>= 2026.2.14` ## Details The non-sandbox path resolution in `apply_patch` did not enforce workspace containment. Inputs like `../../...` or absolute paths could escape the working directory in non-sandboxed mode. ## Impact Practical impact depends on deployment and who can trigger to

O3 Security · Impact-Aware SCA

Is GHSA-r5fq-947m-xm57 in your dependencies?

O3 detects GHSA-r5fq-947m-xm57 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

GHSA-r5fq-947m-xm57

EPSS Exploitation Probability

Blast Radius

Description

Summary

Affected Packages / Versions

Details

Impact

Workarounds

Configuration Note

Fix

Credits

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-r5fq-947m-xm57 in your dependencies?