# CVE-2026-26032: Apache Ivy: PackagerResolver path traversal vulnerability

> An attacker with access to a packager repository can overwrite files outside the build directory by injecting path traversal sequences into Ivy coordinates.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-j482-hm6j-v5jj, SUSE-SU-2026:22858-1, SUSE-SU-2026:3225-1, UBUNTU-CVE-2026-26032, openSUSE-SU-2026:11326-1, openSUSE-SU-2026:21424-1

## What is CVE-2026-26032?

CVE-2026-26032 is a medium-severity path traversal vulnerability in Apache Ivy, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-26032?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-commons-compress` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.28.0-150200.3.19.1 |
| `apache-ivy` | SUSE:Linux Enterprise Module for Development Tools 15 SP7 | All versions | 2.6.0-150200.3.12.1 |
| `apache-ivy` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.6.0-160000.1.1 |
| `apache-ivy` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.6.0-160000.1.1 |
| `apache-ivy` | openSUSE:Leap 16.0 | All versions | 2.6.0-160000.1.1 |
| `apache-ivy` | openSUSE:Tumbleweed | All versions | 2.6.0-1.1 |

Products: Apache Ivy.

## How do I fix CVE-2026-26032?

Upgrade to a fixed version.

## Is CVE-2026-26032 being exploited?

There is no known exploitation of CVE-2026-26032 in the wild and no public exploit code.

## Other vulnerabilities in Apache Ivy

- [CVE-2022-37865](https://insights.sbomify.com/CVE-2022-37865/): Apache Ivy allows creating/overwriting any file on the system (critical 9.1)
- [CVE-2022-46751](https://insights.sbomify.com/CVE-2022-46751/): Apache Ivy: XML External Entity vulnerability in Apache Ivy (high 8.2)
- [CVE-2022-37866](https://insights.sbomify.com/CVE-2022-37866/): Apache Ivy allows path traversal in the presence of a malicious repository (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26032 and fix it if it is affected.

What it is: CVE-2026-26032 is a medium-severity path traversal vulnerability in Apache Ivy, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26032 in the wild and no public exploit code.

Affected product: Apache Ivy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26032/ (Markdown: https://insights.sbomify.com/CVE-2026-26032/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26032
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26032
- OSV: https://osv.dev/vulnerability/CVE-2026-26032

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26032/
Summaries are generated and may contain mistakes; the official description above is the record.