Arbitrary file write via prefix-matched extraction paths
Published Mar 25, 2026 · Updated Mar 25, 2026
Path traversal in pf4j before 3.14.1 allows remote attackers to write files outside the extraction directory via a crafted ZIP archive. Unzip.extract() joins each entry name to the destination and accepts a canonical path when its string merely shares the destination prefix, so a ../ entry targeting a similarly named sibling directory passes validation. The application must pass an attacker-controlled archive to this library routine; resulting writes carry the application's filesystem permissions.
Summary
What happened
Path traversal in pf4j before 3.14.1 allows remote attackers to write files outside the extraction directory via a crafted ZIP archive. Unzip.extract() joins each entry name to the destination and accepts a canonical path when its string merely shares the destination prefix, so a ../ entry targeting a similarly named sibling directory passes validation. The application must pass an attacker-controlled archive to this library routine; resulting writes carry the application's filesystem permissions.
The record
- CVE
- CVE-2025-70952
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-23, CWE-22
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Sibling-directory prefix bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo