CVE-2026-26032: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Apache Software Foundation Apache Ivy
The PackagerResolver of Apache Ivy is able to download online artifacts and to (re)package them in a format defined by a packager.xml file. This repackaging is done by an Ant script, which is stored in a subdirectory of the configured "buildRoot" directory. This subdirectory is calculated based on modules coordinates, like the organisation, name or version. If one of the coordinates contains "../" sequences - which are valid characters for Ivy coordinates in general- it is possible to break out of the configured "buildRoot" directory where other files can be overwritten. In order to exploit this vulnerability an attacker needs to have access to a packager repository and add or modify the coordinates in ivy.xml files to have such "../" sequences. Users of Apache Ivy 2.0.0 to 2.5.3 (inclusive) should upgrade to Ivy 2.6.0.
AI Analysis
Technical Summary
The PackagerResolver in Apache Ivy downloads and repackages artifacts using an Ant script stored in a subdirectory under a configured buildRoot directory. The subdirectory path is derived from module coordinates such as organisation, name, or version. If these coordinates include '../' sequences, which are valid in Ivy coordinates, it is possible to traverse directories outside the buildRoot, potentially overwriting files outside the intended directory. Exploitation requires the attacker to have the ability to add or modify coordinates in ivy.xml files within a packager repository. Versions 2.0.0 through 2.5.3 are affected, with a fix available in version 2.6.0.
Potential Impact
An attacker with access to a packager repository can exploit this vulnerability to perform path traversal, allowing overwriting of arbitrary files outside the designated buildRoot directory. This could lead to unauthorized modification of files on the system where Apache Ivy is running, potentially impacting system integrity or availability depending on the files overwritten.
Mitigation Recommendations
Users should upgrade Apache Ivy to version 2.6.0 or later, where this path traversal vulnerability is fixed. No other official remediation or temporary fixes are documented. Until upgrading, restrict access to packager repositories to trusted users to prevent malicious coordinate manipulation.
CVE-2026-26032: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Apache Software Foundation Apache Ivy
Description
The PackagerResolver of Apache Ivy is able to download online artifacts and to (re)package them in a format defined by a packager.xml file. This repackaging is done by an Ant script, which is stored in a subdirectory of the configured "buildRoot" directory. This subdirectory is calculated based on modules coordinates, like the organisation, name or version. If one of the coordinates contains "../" sequences - which are valid characters for Ivy coordinates in general- it is possible to break out of the configured "buildRoot" directory where other files can be overwritten. In order to exploit this vulnerability an attacker needs to have access to a packager repository and add or modify the coordinates in ivy.xml files to have such "../" sequences. Users of Apache Ivy 2.0.0 to 2.5.3 (inclusive) should upgrade to Ivy 2.6.0.
CVSS v3.1
Score 5.4medium
Affected software
pkg:maven/Apache Software Foundation/org.apache.ivy:ivyRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The PackagerResolver in Apache Ivy downloads and repackages artifacts using an Ant script stored in a subdirectory under a configured buildRoot directory. The subdirectory path is derived from module coordinates such as organisation, name, or version. If these coordinates include '../' sequences, which are valid in Ivy coordinates, it is possible to traverse directories outside the buildRoot, potentially overwriting files outside the intended directory. Exploitation requires the attacker to have the ability to add or modify coordinates in ivy.xml files within a packager repository. Versions 2.0.0 through 2.5.3 are affected, with a fix available in version 2.6.0.
Potential Impact
An attacker with access to a packager repository can exploit this vulnerability to perform path traversal, allowing overwriting of arbitrary files outside the designated buildRoot directory. This could lead to unauthorized modification of files on the system where Apache Ivy is running, potentially impacting system integrity or availability depending on the files overwritten.
Mitigation Recommendations
Users should upgrade Apache Ivy to version 2.6.0 or later, where this path traversal vulnerability is fixed. No other official remediation or temporary fixes are documented. Until upgrading, restrict access to packager repositories to trusted users to prevent malicious coordinate manipulation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-02-09T22:55:23.574Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a57dcf368715ace434afb5c
Added to database: 07/15/2026, 19:18:11 UTC
Last enriched: 07/15/2026, 19:33:44 UTC
Last updated: 07/16/2026, 03:45:27 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.