zip Incorrectly Canonicalizes Paths during Archive Extraction Leading to Arbitrary File Write

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.3 · CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:H/SI:H/SA:H · score source

EPSS

• CVE-2025-29787: 0.58% estimated exploitation activity in the next 30 days; percentile 48.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary In the archive extraction routine of affected versions of the zip crate, symbolic links earlier in the archive are allowed to be used for later files in the archive without validation of the final canonicalized path, allowing maliciously crafted archives to overwrite arbitrary files in the file system when extracted. Details This is a variant of the zip-slip vulnerability, we can make the extraction logic step outside of the target directory by creating a symlink to the parent directory and then extracting further files through that symlink. The documentation of the [::zip::read::ZipArchive::extract] method is in my opinion implying this should not happen: "Paths are sanitized with ZipFile::enclosedname." ... [::zip::read::FileOptions::enclosedname] ... is resistant to path-based exploits ... can’t resolve to a path outside the current directory. Most archive software either decline to extract symlinks that traverse out of the directory or defer creation of symlinks after all…

Published by the source

17 Mar 2025, 21:26 UTC

Last modified by the source

19 Mar 2025, 15:51 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-94vh-gphv-8pm8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-29787

Advisory: zip Incorrectly Canonicalizes Paths during Archive Extraction Leading to Arbitrary File Write
IDs: CVE-2025-29787, GHSA-94vh-gphv-8pm8
Record: https://patchnext.com/advisories/cve-2025-29787 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zip 2.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io zip: affected >= 1.3.0, < 2.3.0; fixed in 2.3.0

## Suggested inspection (read-only)
- crates.io zip: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zip.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-94vh-gphv-8pm8 (GitHub-reviewed advisory GHSA-94vh-gphv-8pm8 lists affected ranges: crates.io zip >=1.3.0 <2.3.0)

Commands are suggestions: review each one before running it.