GHSA-5458-7hh9-v7p4 — pf4j
Fix: pf4j/pf4j@20c2f80GHSA-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.
pf4j is vulnerable to Path Traversal or Zip Slip attack through improper handling of zip entry names
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
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.
Real-World Exposure
org.pf4j:pf4jReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.pf4j:pf4j | all versions | 3.14.1org.pf4j:pf4j:3.14.1 |
Detection & mitigation playbook
Open-source dependencyDetect
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
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-5458-7hh9-v7p4 can be triaged on real exposure rather than presence alone.
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
Is GHSA-5458-7hh9-v7p4 in your dependencies?
O3 Security finds GHSA-5458-7hh9-v7p4 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.