How severe is GHSA-5458-7hh9-v7p4?

No CVSS score has been assigned to GHSA-5458-7hh9-v7p4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5458-7hh9-v7p4?

GHSA-5458-7hh9-v7p4 affects the following packages: org.pf4j:pf4j (Maven). Ecosystems affected: Maven.

How do I fix GHSA-5458-7hh9-v7p4?

Update org.pf4j:pf4j to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5458-7hh9-v7p4 is resolved across your whole dependency graph.

How do I detect GHSA-5458-7hh9-v7p4 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.pf4j:pf4j. 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-5458-7hh9-v7p4 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-5458-7hh9-v7p4?

O3 pinpoints whether GHSA-5458-7hh9-v7p4 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-5458-7hh9-v7p4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5458-7hh9-v7p4 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 type of vulnerability is GHSA-5458-7hh9-v7p4?

GHSA-5458-7hh9-v7p4 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-5458-7hh9-v7p4 published, and has it been updated?

GHSA-5458-7hh9-v7p4 was published on March 25, 2026 and was last updated on April 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-5458-7hh9-v7p4

GHSA-5458-7hh9-v7p4 is a Path Traversal vulnerability in org.pf4j:pf4j. O3 Security confirms whether GHSA-5458-7hh9-v7p4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

pf4j is vulnerable to Path Traversal or Zip Slip attack through improper handling of zip entry names

Also known asCVE-2025-70952

Published

Mar 25, 2026

Updated

Apr 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

☕org.pf4j:pf4j

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

pf4j before 20c2f80 has a path traversal vulnerability in the extract() function of Unzip.java, where improper handling of zip entry names can allow directory traversal or Zip Slip attacks, due to a lack of proper path normalization and validation.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.pf4j:pf4j`	all versions	3.14.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.pf4j:pf4j. 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 org.pf4j:pf4j to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5458-7hh9-v7p4 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-5458-7hh9-v7p4 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-5458-7hh9-v7p4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-5458-7hh9-v7p4 in your dependencies?

O3 detects GHSA-5458-7hh9-v7p4 across Maven 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