CVE-2026-106070

Node2Shell

Read full description

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 3.7 (LOW)

Attention and evidence

HYPE SCORE

3.4/10

REALITY · THREAT PRIORITY

1.3/10

General review priority; not probability

Evidence confidence: Insufficient evidence

Why this priority?

Technical severity: CVSS 3.7: +1.30
Fresh EPSS: 0.37%: +0.01

General review priority, not probability, victim count or asset-specific risk. A range covers missing CVSS/EPSS inputs within the current evidence state.

Sources: 2 documents and public datasets.

Hype components

Headline sample (25%)

50/100

Press, 30 days (60%)

10/100

Grounded branding (15%)

100/100

HYPE TOTAL34/100

Sources and documents

FortiGuard Labs | FortiGuard Center - IR Advisories

Press · 26 Oct 2026, 07:00 · Node2Shell CVEs

Una Al Día

Press · 23 Oct 2026, 08:01 · Node.js corrige fallos graves de TLS y Brotli en sus ramas 26, 24 y 22

Score evolution

● Hype ● Reality

Earlier evidence-support scores are retained in history; this chart shows only the current priority definition.

First record: hype 3.4 · reality 1.3 (2026-11-02 15:14). The curve appears once the score changes.

Public exploit evidence

Public exploit entries / repo candidates

Evidence context and dated references

Reality is general threat/review priority, combining observed exploitation, CVSS severity and fresh EPSS. Evidence confidence is separate. This is not calibrated risk, a victim count or an asset-specific assessment. A range reflects missing numeric inputs. Published 13 days ago. Exploitation evidence usually takes weeks to show up: a low reality score can mean there is no data yet, not that the flaw is mild.

Evidence in context

Confidence in exploitation evidence: Insufficient evidence
Priority basis: Exploitation in attacks unconfirmed; CVSS 3.7; EPSS 0.4%
Attention, last 30 days: 2 distinct story titles; 2 press documents; 2 publisher domains.
Technical potential: network access, no prior privileges, no user interaction, additional attack conditions.
Observed activity: No exploitation observation is recorded.
Known scale: Not quantified.
Evidence confidence basis: Insufficient evidence

Score evaluated: 2026-11-05 13:59:51.107056+00:00 · EPSS snapshot: 2026-11-05T12:03:04Z

Source event timeline

First press mention

23 Oct 2026, 08:01

Published

23 Oct 2026, 16:15

Latest press mention

26 Oct 2026, 07:00

Score calculated

05 Nov 2026, 13:59

Name

Node2Shell