How severe is GHSA-xw4p-pw82-hqr7?

GHSA-xw4p-pw82-hqr7 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xw4p-pw82-hqr7?

GHSA-xw4p-pw82-hqr7 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-xw4p-pw82-hqr7?

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

How do I detect GHSA-xw4p-pw82-hqr7 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-xw4p-pw82-hqr7 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-xw4p-pw82-hqr7?

O3 pinpoints whether GHSA-xw4p-pw82-hqr7 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-xw4p-pw82-hqr7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xw4p-pw82-hqr7 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-xw4p-pw82-hqr7?

GHSA-xw4p-pw82-hqr7 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 3th 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-xw4p-pw82-hqr7?

GHSA-xw4p-pw82-hqr7 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-xw4p-pw82-hqr7 published, and has it been updated?

GHSA-xw4p-pw82-hqr7 was published on March 2, 2026 and was last updated on March 6, 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-xw4p-pw82-hqr7

HIGH

OpenClaw's sandbox skill mirroring path traversal vulnerability could write outside the sandbox workspace

Also known asCVE-2026-28457

Published

Mar 2, 2026

Updated

Mar 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk3th percentile+0.09%

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

Overview

In affected versions, OpenClaw’s sandbox skill mirroring used the skill’s frontmatter name as part of the destination path when copying skills into the sandbox workspace. A crafted skill name containing traversal segments (for example ../) or an absolute path could cause the copy to write outside <sandbox_workspace>/skills/.

Impact

Files may be written outside the sandbox workspace root (within the permissions of the user running OpenClaw).

Attack Requirements

Attacker can provide a skill package (controls SKILL.md frontmatter).
Victim runs with sandbox enabled and skill mirroring into the sandbox workspace.

Affected Packages / Versions

openclaw (npm): < 2026.2.14

Fixed In

openclaw (npm): >= 2026.2.14

Fix Commit(s)

3eb6a31b6fcf8268456988bfa8e3637d373438c2

OpenClaw thanks @1seal for reporting.

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-xw4p-pw82-hqr7 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-xw4p-pw82-hqr7 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-xw4p-pw82-hqr7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Overview In affected versions, OpenClaw’s sandbox skill mirroring used the skill’s frontmatter `name` as part of the destination path when copying skills into the sandbox workspace. A crafted skill name containing traversal segments (for example `../`) or an absolute path could cause the copy to write outside `<sandbox_workspace>/skills/`. ## Impact - Files may be written outside the sandbox workspace root (within the permissions of the user running OpenClaw). ## Attack Requirements - Attacker can provide a skill package (controls `SKILL.md` frontmatter). - Victim runs with sandbox ena

O3 Security · Impact-Aware SCA

Is GHSA-xw4p-pw82-hqr7 in your dependencies?

O3 detects GHSA-xw4p-pw82-hqr7 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