Skip to content

← Actionable
High, CVSS 7.4amended

zip: Arbitrary file write outside the extraction directory, because ZipArchive::extract validates symlink targets lexically.

CVE-2026-115908GHSA-hjqx-j4rw-g7xv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (zip 9.0.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • crates.io zip

    Affected
    >= 7.2.0, < 9.0.0
    Fixed in
    9.0.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
  • CVE-2026-115908: 0.43% estimated exploitation activity in the next 30 days; percentile 37.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary - Verified version: zip `9.0.0-pre3` - Affected versions: `7.2.0` and later - Precondition: The attacker knows (or can guess) the absolute path of the extraction destination The validation applied to symlinks is purely lexical. As a result, an attacker can write arbitrary files outside the extraction directory through a symlink. Exploitation requires the attacker to know (or guess) the absolute path of the destination, but this is realistic in practice: CI workspaces, `/opt/app`, a fixed Downloads path, and so on. > Impact extends further on Windows (verified on real hardware for both the separate-drive and UNC-share cases): > Because `simplified_components` discards the `Prefix` component, paths like `D:\ ` or a UNC path `\\attacker\share\ ` pass the `starts_with` check. > As a result, `outpath.push` gets replaced onto a different drive/remote share, so a single symlink is enough — no intermediate symlink chain is required. > That said, creating a…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-hjqx-j4rw-g7xv

  2. Revision 1 · created ·

    Published from ghsa record GHSA-hjqx-j4rw-g7xv

Agent brief

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

# Patch Next advisory brief: CVE-2026-115908

Advisory: zip: Arbitrary file write outside the extraction directory, because ZipArchive::extract validates symlink targets lexically.
IDs: CVE-2026-115908, GHSA-hjqx-j4rw-g7xv
Record: https://patchnext.com/advisories/cve-2026-115908 (revision 2, source checked 30 Oct 2026, 07:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zip 9.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io zip: affected >= 7.2.0, < 9.0.0; fixed in 9.0.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-hjqx-j4rw-g7xv (GitHub-reviewed advisory GHSA-hjqx-j4rw-g7xv lists affected ranges: crates.io zip >=7.2.0 <9.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-hjqx-j4rw-g7xv (OSV record GHSA-hjqx-j4rw-g7xv lists affected ranges: crates.io zip >=7.2.0 <9.0.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…