How severe is GHSA-f6pf-4gjx-c94r?

No CVSS score has been assigned to GHSA-f6pf-4gjx-c94r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f6pf-4gjx-c94r?

GHSA-f6pf-4gjx-c94r affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-f6pf-4gjx-c94r?

Update openclaw to 2026.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f6pf-4gjx-c94r is resolved across your whole dependency graph.

How do I detect GHSA-f6pf-4gjx-c94r 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-f6pf-4gjx-c94r 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-f6pf-4gjx-c94r?

O3 pinpoints whether GHSA-f6pf-4gjx-c94r 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-f6pf-4gjx-c94r actively exploited in the wild?

No public exploit code has been indexed for GHSA-f6pf-4gjx-c94r 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-f6pf-4gjx-c94r published, and has it been updated?

GHSA-f6pf-4gjx-c94r was published on April 3, 2026 and was last updated on April 3, 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-f6pf-4gjx-c94r

OpenClaw: Media Parsing Path Traversal Leads to Arbitrary File Read

Published

Apr 3, 2026

Updated

Apr 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

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

openclawnpm

3.7Mdownloads / week

Description

Summary

OpenClaw <= 2026.3.24 Media Parsing Path Traversal to Arbitrary File Read

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version: 2026.3.31
Vulnerable version range: <=2026.3.24
Patched versions: >= 2026.3.28
First stable tag containing the fix: v2026.3.28

Fix Commit(s)

4797bbc5b96e2cca5532e43b58915c051746fe37 — 2026-03-25T13:35:16-06:00

Release Process Note

The fix is already present in released version 2026.3.28.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Summary OpenClaw <= 2026.3.24 Media Parsing Path Traversal to Arbitrary File Read ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version: `2026.3.31` - Vulnerable version range: `<=2026.3.24` - Patched versions: `>= 2026.3.28` - First stable tag containing the fix: `v2026.3.28` ## Fix Commit(s) - `4797bbc5b96e2cca5532e43b58915c051746fe37` — 2026-03-25T13:35:16-06:00 ## Release Process Note - The fix is already present in released version `2026.3.28`.

O3 Security · Impact-Aware SCA

Is GHSA-f6pf-4gjx-c94r in your dependencies?

O3 detects GHSA-f6pf-4gjx-c94r 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