Vulnerability · CVE-2026-106070
A flaw in the Node.js API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails.
Published Oct 23, 2026 · catalog updated Oct 24, 2026 · A flaw in the
Last checked Nov 4, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-106070. EPSS is 0.37%. Act only if a listed version of A flaw in the is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (A flaw in the).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Low3.7
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.37%
- Remediation
- Advisory link
- Affected products
- Alpine:v3.23 nodejs · Alpine:v3.24 nodejs
A flaw in the Node.js API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When 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**.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Alpine:v3.23 nodejs0 → 24.22.1-r0
- Alpine:v3.24 nodejs0 → 24.22.1-r0
How to fix CVE-2026-106070
Upgrade
CVE-2026-106070 lists a fix boundary at 24.22.1-r0. Compare the installed build with that boundary before you change production.
Version check
Fixed in 24.22.1-r0 · 1 other ranges on the advisory
Advisory
Open the bsi record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-106070. EPSS is 0.37%. Act only if a listed version of A flaw in the is installed.
Which versions are affected?
Compare what you have installed with 0 → 24.22.1-r0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 23, 2026 · Trivy Vulnerability DB
Detected
A flaw in the Node.js API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When 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 r
Oct 24, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 24.22.1-r0; nodejs fixed in 24.22.1-r0
Oct 24, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 24.22.1-r0
Oct 24, 2026 · Trivy Vulnerability DB
Updated
A flaw in the Node.js API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When 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 r
Sources
- BSI CERT-BundGovernment advisoryCVE-2026-106070
Node.js: Mehrere Schwachstellen
wid.cert-bund.de - CVE.orgVulnerability recordCVE-2026-106070
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-106070
30-day exploitation probability 0.37%
first.org - Trivy Vulnerability DBPackage advisoryALPINE-CVE-2026-106070
A flaw in the Node.js API can cause it to return bytes that do not belong to the requested entry after the local and central header validation fails. When is read on an archive whose local header does not match its central directory, either directly or while compacting the archiv
osv.dev
References
Freshness
Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- BSI CERT-BundNov 4, 2026
- FIRST EPSSNov 4, 2026
- Trivy Vulnerability DBOct 25, 2026
- CVE.orgOct 24, 2026