How severe is GHSA-3pxq-f3cp-jmxp?

GHSA-3pxq-f3cp-jmxp has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-3pxq-f3cp-jmxp?

GHSA-3pxq-f3cp-jmxp affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-3pxq-f3cp-jmxp?

Update openclaw to 2026.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3pxq-f3cp-jmxp is resolved across your whole dependency graph.

How do I detect GHSA-3pxq-f3cp-jmxp 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-3pxq-f3cp-jmxp 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-3pxq-f3cp-jmxp?

O3 pinpoints whether GHSA-3pxq-f3cp-jmxp 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-3pxq-f3cp-jmxp actively exploited in the wild?

No public exploit code has been indexed for GHSA-3pxq-f3cp-jmxp 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-3pxq-f3cp-jmxp?

GHSA-3pxq-f3cp-jmxp 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.

When was GHSA-3pxq-f3cp-jmxp published, and has it been updated?

GHSA-3pxq-f3cp-jmxp was published on March 3, 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-3pxq-f3cp-jmxp

MEDIUM

OpenClaw: Unified root-bound write hardening for browser output and related path-boundary flows

Also known asCVE-2026-22180

Published

Mar 3, 2026

Updated

Mar 18, 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.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.3Mdownloads / week

Description

Summary

A path-confinement bypass in browser output handling allowed writes outside intended roots in openclaw versions up to and including 2026.3.1.

The fix unifies root-bound, file-descriptor-verified write semantics and canonical path-boundary validation across browser output and related install/skills write paths.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version at triage time: 2026.3.1
Affected range: <= 2026.3.1
Patched release: 2026.3.2 (released)

Fix Commit(s)

104d32bb64cdf19d5e77f70553a511a2ae90ad1c

Technical Notes

Browser output writes now use root-bound, fd/inode-verified commit flow.
Install + skills path checks now share canonical in-base validation to reduce drift and close equivalent escape surfaces.
Added regression coverage for symlink-rebind and root-bound source-path write behavior.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

### Summary A path-confinement bypass in browser output handling allowed writes outside intended roots in `openclaw` versions up to and including `2026.3.1`. The fix unifies root-bound, file-descriptor-verified write semantics and canonical path-boundary validation across browser output and related install/skills write paths. ### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version at triage time: `2026.3.1` - Affected range: `<= 2026.3.1` - Patched release: `2026.3.2` (released) ### Fix Commit(s) - `104d32bb64cdf19d5e77f70553a511a2ae90ad1c` ### Technical

O3 Security · Impact-Aware SCA

Is GHSA-3pxq-f3cp-jmxp in your dependencies?

O3 detects GHSA-3pxq-f3cp-jmxp 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