How severe is CVE-2026-26032?

CVE-2026-26032 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2026-26032 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-26032?

CVE-2026-26032 affects Apache Ivy. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-26032?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-26032 published?

CVE-2026-26032 was published on 2026-07-15 and last updated on 2026-07-16.

CVE-2026-26032

CVE-2026-26032 is a medium-severity vulnerability in Apache Ivy with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.

Key facts

Severity: Medium (CVSS 3.x base score 5.4)
EPSS exploit prediction: 1% (41st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-22
Affected product: Apache Ivy
Published: 2026-07-15
Last modified: 2026-07-16

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.

Frequently asked questions

What is CVE-2026-26032?: 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.
How severe is CVE-2026-26032?: CVE-2026-26032 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2026-26032 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-26032?: CVE-2026-26032 affects Apache Ivy. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-26032?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-26032 published?: CVE-2026-26032 was published on 2026-07-15 and last updated on 2026-07-16.

References

Affected products (1)

cpe:2.3:a:apache:ivy:*:*:*:*:*:*:*:*

More vulnerabilities in Apache Ivy

CVE-2022-37865 — Critical (CVSS 9.1): With Apache Ivy 2.4.0 an optional packaging attribute has been introduced that allows artifacts to be unpacked on the…
CVE-2022-46751 — High (CVSS 8.2): Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in…
CVE-2022-37866 — High (CVSS 7.5): When Apache Ivy downloads artifacts from a repository it stores them in the local file system based on a user-supplied…

All CVEs affecting Apache Ivy →

Other CWE-22 (Path Traversal) vulnerabilities

CVE-2026-76606 — Critical (CVSS 10.0): Joomla Extension - fabrikar.com - Path Traversal via image element in Fabrik < 4.7.3 - ???.
CVE-2026-18051 — Critical (CVSS 10.0): The W3 Total Cache WordPress plugin before 2.10.5 does not properly validate the request path it uses to build cache…
CVE-2026-74764 — Critical (CVSS 10.0): Pandora contains a path traversal vulnerability in its TAR archive extraction functionality. When processing a…
CVE-2026-16940 — Critical (CVSS 10.0): The Custom Fields WordPress plugin before 1.5.1 does not validate a user-supplied file path before deletion, allowing…
CVE-2026-67429 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.6, image.download and related…
CVE-2026-59555 — Critical (CVSS 10.0): Unauthenticated Arbitrary File Deletion in Participants Database <= 2.7.8.3 versions.

Browse all CWE-22 (Path Traversal) vulnerabilities →