CVE-2026-106070 Affecting nodejs-26 package, versions <26.12.1-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.35% (29th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-NODEJS26-21723704
  • published27 Oct 2026
  • disclosed23 Oct 2026

Introduced: 23 Oct 2026

NewCVE-2026-106070  (opens in a new tab)

How to fix?

Upgrade Chainguard nodejs-26 to version 26.12.1-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs-26 package and not the nodejs-26 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1