File overwrite via unvalidated module coordinates
Published Jul 15, 2026 · Updated Jul 15, 2026
Path traversal in Apache Ivy 2.0.0 through 2.5.3 allows remote authenticated users to overwrite files via crafted module coordinates. PackagerResolver derives an Ant-script directory beneath buildRoot from organization, module, and version values without rejecting ../ sequences. Exploitation requires access to modify ivy.xml coordinates in a packager repository, and writes are limited to locations writable by the Ivy process.
Summary
What happened
Path traversal in Apache Ivy 2.0.0 through 2.5.3 allows remote authenticated users to overwrite files via crafted module coordinates. PackagerResolver derives an Ant-script directory beneath buildRoot from organization, module, and version values without rejecting ../ sequences. Exploitation requires access to modify ivy.xml coordinates in a packager repository, and writes are limited to locations writable by the Ivy process.
The record
- CVE
- CVE-2026-26032
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Ivy
- Classifications
- CWE-22, T1195.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <=2.5.3
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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