Node.js ZipFile returns attacker-controlled prefix bytes after failed ZIP header validation

Exploitation

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

CVSS

not scored

EPSS

• CVE-2026-106070: 0.37% estimated exploitation activity in the next 30 days; percentile 30.59 (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.

A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When `zipEntry.modified` is read on an archive whose local header does not match its central directory, either directly or while compacting the archive, the validation error is caught but the parsed local header is left cached without a content offset. A later content read then returns attacker-controlled bytes from the start of the file instead of rejecting the archive, and CRC-32 verification still passes because the attacker controls the central directory CRC. A Node.js-based scanner can therefore approve different content from what another ZIP implementation extracts from the same archive. This vulnerability affects Node.js 26.x.

Published by the source

21 Oct 2026, 00:00 UTC

Last modified by the source

29 Oct 2026, 10:56 UTC

Source last checked

30 Oct 2026, 07:10 UTC

1. Revision 3 · amended · 30 Oct 2026

   Amended from osv record BIT-node-min-2026-106070

2. Revision 2 · amended · 30 Oct 2026

   Amended from osv record BIT-node-2026-106070

3. Revision 1 · created · 29 Oct 2026

   Published from vendor_advisory record nodejs-security-wg:core:199

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

# Patch Next advisory brief: CVE-2026-106070

Advisory: Node.js ZipFile returns attacker-controlled prefix bytes after failed ZIP header validation
IDs: CVE-2026-106070
Record: https://patchnext.com/advisories/cve-2026-106070 (revision 3, 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: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: node-min 26.12.1; node 26.12.1; node 26.12.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami node-min: affected >= 25.0.0, < 26.12.1; fixed in 26.12.1
- runtime node: affected >= 26.0.0, < 26.12.1; fixed in 26.12.1
- Bitnami node: affected >= 25.0.0, < 26.12.1; fixed in 26.12.1

## Suggested inspection (read-only)
- Bitnami node-min: check the installed version with your package manager.
- runtime node: check the installed version with your package manager.
- Bitnami node: 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 node-min, node.
- 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://nodejs.org/dist/index.json (The nodejs.org release index dates the first patched release for CVE-2026-106070 to 2026-10-21.)
- Verified: https://raw.githubusercontent.com/nodejs/security-wg/main/vuln/core/199.json (Node.js security working group core entry 199 lists CVE-2026-106070 affecting node >=26.0.0 <26.12.1)
- Verified: https://osv.dev/vulnerability/BIT-node-2026-106070 (OSV record BIT-node-2026-106070 lists affected ranges: Bitnami node >=25.0.0 <26.12.1 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-node-min-2026-106070 (OSV record BIT-node-min-2026-106070 lists affected ranges: Bitnami node-min >=25.0.0 <26.12.1 (fixed))

Commands are suggestions: review each one before running it.