dbcve.org
IvyApplication · Apache

CVE-2026-26032

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 2.6.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Path traversal vulnerability in Apache Ivy's PackagerResolver allows attackers to escape the configured buildRoot directory by including '../' sequences in module coordinates (organization, name, or version). The PackagerResolver uses these coordinates to create subdirectories for storing Ant scripts that repackage downloaded artifacts, and insufficient validation enables arbitrary file overwrite.

MitigationUpgrade Apache Ivy from version 2.0.0-2.5.3 to version 2.6.0 which contains the fix for this vulnerability. Additionally, implement input validation on module coordinates to reject path traversal sequences.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IvyApplication
Affected:>= 2.0.0, < 2.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Ivy version
    Locate the ivy JAR file in your project dependencies or build environment and check its version (typically found in filename like ivy-2.x.x.jar or in pom.xml/META-INF/MANIFEST.MF)
    Affected if The installed version is 2.0.0 or higher but lower than 2.6.0
  2. Confirm PackagerResolver is in use
    Search your Ivy settings XML file (commonly ivysettings.xml) for a <packager> resolver element or programmatically check for PackagerResolver in your resolver chain
    Affected if PackagerResolver is configured and actively used for dependency resolution
  3. Inspect module coordinate sources
    Review any Ivy resolve calls or dependency declarations that pull from repositories using PackagerResolver, particularly those accepting user-supplied organization, module, or revision values
    Affected if External or untrusted module coordinates can be passed to the PackagerResolver without validation

You are affected if you run Apache Ivy versions 2.0.0 through 2.5.x with PackagerResolver enabled and accept module coordinates from any source that could contain '../' sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.0 or later
Fixed in 2.6.0
Interim mitigation

Upgrade Apache Ivy from version 2.0.0-2.5.3 to version 2.6.0 which contains the fix for this vulnerability. Additionally, implement input validation on module coordinates to reject path traversal sequences.

Recommended fix High confidence

Ivy 2.6.0

  1. Upgrade Apache Ivy from any version >= 2.0.0 and < 2.6.0 to version 2.6.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ivy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26032 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26032 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data