How severe is GHSA-jxrq-8fm4-9p58?

No CVSS score has been assigned to GHSA-jxrq-8fm4-9p58 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jxrq-8fm4-9p58?

GHSA-jxrq-8fm4-9p58 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-jxrq-8fm4-9p58?

Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jxrq-8fm4-9p58 is resolved across your whole dependency graph.

How do I detect GHSA-jxrq-8fm4-9p58 in my npm dependencies?

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.

How do I mitigate GHSA-jxrq-8fm4-9p58 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-jxrq-8fm4-9p58?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jxrq-8fm4-9p58 can be triaged on real exposure rather than presence alone.

Is GHSA-jxrq-8fm4-9p58 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jxrq-8fm4-9p58 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.

When was GHSA-jxrq-8fm4-9p58 published, and has it been updated?

GHSA-jxrq-8fm4-9p58 was published on March 3, 2026 and was last updated on March 4, 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

Not in CISA KEV

GHSA-jxrq-8fm4-9p58 — openclaw

Fix: openclaw/openclaw@4b226b7

GHSA-jxrq-8fm4-9p58 is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: Zip extraction symlink traversal could write outside destination

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, 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

openclawnpm

3.1Mdownloads / week

Description

Summary

A path confinement bypass in OpenClaw ZIP extraction allowed writes outside the intended destination when a pre-existing symlink was present under the extraction root.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version at triage time: 2026.2.21-2
Affected versions: <= 2026.2.21-2
Planned patched version for next release: 2026.2.22

Technical Details

The vulnerable path was in src/infra/archive.ts ZIP extraction logic. Output-path checks were lexical, but writes could still traverse an existing symlink in destination path segments.

The fix blocks this by:

rejecting symlink traversal in destination path segments,
validating resolved destination paths remain inside the extraction root,
using no-follow file opens for ZIP output writes where supported,
adding a regression test for pre-seeded destination symlink traversal.

Impact

Type: Arbitrary file write outside extraction root via symlink traversal during ZIP extraction.
Preconditions: attacker-controlled archive extraction plus pre-existing symlink in destination path.

Fix Commit(s)

4b226b74f5fd3b106a83a6347fd404172e2fd246

Release Process Note

Patched version is pre-set to the planned next release (2026.2.22). Once npm release 2026.2.22 is published, the advisory can be published without further field edits.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.22`npm install openclaw@2026.2.22`

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jxrq-8fm4-9p58 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jxrq-8fm4-9p58 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-jxrq-8fm4-9p58. 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 OpenClaw ZIP extraction allowed writes outside the intended destination when a pre-existing symlink was present under the extraction root. ### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version at triage time: `2026.2.21-2` - Affected versions: `<= 2026.2.21-2` - Planned patched version for next release: `2026.2.22` ### Technical Details The vulnerable path was in `src/infra/archive.ts` ZIP extraction logic. Output-path checks were lexical, but writes could still traverse an existing symlink in destination path seg

O3 Security · Impact-Aware SCA

Is GHSA-jxrq-8fm4-9p58 in your dependencies?

O3 Security finds GHSA-jxrq-8fm4-9p58 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works