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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5458-7hh9-v7p4 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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 is the EPSS score for GHSA-5458-7hh9-v7p4?

GHSA-5458-7hh9-v7p4 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th 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-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 September 10, 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

Not in CISA KEV

pf4j is vulnerable to Path Traversal or Zip Slip attack through improper handling of zip entry namesGHSA-5458-7hh9-v7p4

Fix: pf4j/pf4j@20c2f80

GHSA-5458-7hh9-v7p4 is a Path Traversal vulnerability in org.pf4j:pf4j. A fix is available for org.pf4j:pf4j — see the affected versions and patch details below.

Also known asCVE-2025-70952

Published

Mar 25, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5458-7hh9-v7p4.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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`org.pf4j:pf4j:3.14.1`

Affected Products

1 product · 1 configurations

Application

pf4jpf4j_project

< 3.14.1

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

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

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works