Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS)

CVE-2026-77301GHSA-7q85-xj36-vmfc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (adm-zip 0.6.1), 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.

Add to your agent

Affected packages

  • npm adm-zip

    Affected
    < 0.6.1
    Fixed in
    0.6.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-77301: 0.61% estimated exploitation activity in the next 30 days; percentile 49.23 (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 adm-zip allocates an entry's output buffer from the declared uncompressed size (central-directory size field) before validating it against the actual data. A tiny crafted ZIP that declares a huge uncompressed size forces a multi-gigabyte allocation from a few bytes. Impact On adm-zip 0.5.17 (latest), Node 24, a 105-byte ZIP with one stored entry declaring size = 1,774,399,200 makes new AdmZip(buf).getEntries()[0].getData() commit ~1.8 GB of resident memory in ~4.4 s before throwing Error: ADM-ZIP: CRC32 checksum failed, roughly 16 million times the input size. Because the buffer is committed before any validation, on a memory-constrained host (containers, serverless, small VMs) the allocation OOM-kills the process before the CRC check (uncatchable), and concurrent requests can exhaust memory even on larger hosts. Any service that reads entries from untrusted ZIPs is exposed to a remote denial of service. Steps to reproduce Attachments are not supported in the advisory form,…

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

    Amended from ghsa record GHSA-7q85-xj36-vmfc

  2. Revision 2 · amended ·

    Amended from osv record GHSA-7q85-xj36-vmfc

  3. Revision 1 · created ·

    Published from ghsa record GHSA-7q85-xj36-vmfc

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-77301

Advisory: adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS)
IDs: CVE-2026-77301, GHSA-7q85-xj36-vmfc
Record: https://patchnext.com/advisories/cve-2026-77301 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: adm-zip 0.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm adm-zip: affected < 0.6.1; fixed in 0.6.1

## Suggested inspection (read-only)
- `npm ls adm-zip --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 adm-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-7q85-xj36-vmfc (GitHub-reviewed advisory GHSA-7q85-xj36-vmfc lists affected ranges: npm adm-zip >=0 <0.6.1)
- Verified: https://osv.dev/vulnerability/GHSA-7q85-xj36-vmfc (OSV record GHSA-7q85-xj36-vmfc lists affected ranges: npm adm-zip >=0 <0.6.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…