CVE-2026-26032 json
Apache Ivy: PackagerResolver path traversal vulnerability
published 2026-07-15 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-44763
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- apache ivy 2.6.0
- apache-ivy SLE Module for Development Tools 15 SP7 2.6.0-150200.3.12.1
- apache-commons-compress SLE Module for Basesystem 15 SP7 1.28.0-150200.3.19.1
- apache-ivy SLES for SAP applications 16.0, SLES 16.0 2.6.0-160000.1.1
suse advisories SUSE-SU-2026:3225-1SUSE-SU-2026:22858-1
- apache-ivy openSUSE Leap 16.0 2.6.0-160000.1.1
- apache-ivy openSUSE Tumbleweed 2.6.0-1.1
opensuse advisories openSUSE-SU-2026:21424-1openSUSE-SU-2026:11326-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-26032 updated cvss 5.4
Apache Ivy: Apache Ivy: File overwrite vulnerability via malicious module coordinates
-
Red Hat Enterprise Linux 7 apache-ivy-javadoc, apache-ivy 2.3.0-4.el7 Red Hat Enterprise Linux 8 apache-ivy, apache-ivy-javadocaffected: workaround, no fix available “No mitigation is available for this vulnerability.”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected products
- Apache Software Foundation Apache Ivy
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
lists.apache.org
/thread/4d9dzrlnoplvywnyj9x6w84kxg7n3jyq
vendor-advisory, mitigation
-
openwall.com
/lists/oss-security/2026/07/15/5
mailing-list, third-party-advisory
Sources
- CVE List CVE-2026-26032
- NVD CVE-2026-26032
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.