Wiz rejoint Google Cloud : Faire de la magie ensemble

CVE-2026-106070: 
npm Analyse et atténuation des vulnérabilités

Aperçu

CVE-2026-106070 is a denial-of-service vulnerability in the Node.js zlib module caused by improper caching of invalid ZIP local headers. When processing malformed ZIP files, the module may cache invalid headers, potentially enabling attackers to crash applications or cause resource exhaustion. The CVE was inserted into Feedly's threat intelligence feed on October 21, 2026, coinciding with the Node.js v26.12.1 security release. The CVE status is currently listed as "Reserved" and no CVSS score has been publicly assigned yet (Node.js Release, Node.js GitHub).

Détails techniques

The root cause is improper input validation or caching logic within the Node.js zlib module (CWE classification not yet formally assigned, but consistent with improper handling of malformed input, likely CWE-20 or CWE-400). When a malformed ZIP file with invalid local headers is processed, the module incorrectly caches these headers rather than rejecting them, which can lead to unexpected application behavior. Exploitation requires an attacker to supply a crafted ZIP file to an application that processes user-provided archives using Node.js's built-in zlib functionality (Node.js Release, CyberSecurityNews).

Impact

Successful exploitation can cause denial of service through application crashes or resource exhaustion in Node.js applications that process ZIP files using the zlib module. The primary impact is on availability; confidentiality and integrity impacts are not currently documented. Applications that accept user-supplied ZIP archives are most at risk, and widespread use of Node.js in web services means the potential attack surface is significant (Node.js Release, CyberSecurityNews).

Exploitabilité

No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been reported as of the time of disclosure. The CVE is currently in "Reserved" status, and no EPSS score or CISA KEV catalog entry has been identified. Exploitation requires the ability to supply a malformed ZIP file to a vulnerable Node.js application, which is a relatively low barrier in applications that accept file uploads (Node.js GitHub).

Étapes d’exploitation

  1. Reconnaissance: Identify Node.js applications (running versions prior to v26.12.1) that accept user-supplied ZIP file uploads or process ZIP archives from external sources.
  2. Craft malformed ZIP: Create a ZIP file with intentionally invalid or malformed local file headers designed to trigger the improper caching behavior in the zlib module.
  3. Submit malicious file: Upload or otherwise deliver the crafted ZIP file to the target application's file processing endpoint.
  4. Trigger denial of service: The Node.js zlib module processes the malformed headers, caches invalid data, and causes the application to crash or exhaust resources, resulting in a denial-of-service condition (Node.js Release, CyberSecurityNews).

Indicateurs de compromis

  • Logs: Application logs showing repeated crashes or unhandled exceptions originating from the zlib module during ZIP file processing; error messages referencing invalid ZIP local headers.
  • Process: Node.js process unexpectedly terminating or restarting frequently; elevated CPU or memory usage during ZIP file processing operations.
  • Network: Unusual volume of ZIP file upload requests to application endpoints, particularly with small or malformed files.

Atténuation et solutions de contournement

Node.js has addressed this vulnerability in the v26.12.1 security release. Administrators should upgrade affected Node.js installations to v26.12.1 or later as the primary remediation. As a workaround, applications can implement input validation to reject malformed or suspicious ZIP files before passing them to the zlib module, and restrict file upload functionality to trusted users where possible (Node.js Release, Node.js GitHub).

Réactions de la communauté

CyberSecurityNews covered the Node.js security update release, highlighting the zlib flaw among other issues addressed in the v26.12.1 release. The Apereo CAS project also issued a commit referencing the vulnerability, indicating downstream open-source projects are actively responding to the patch (CyberSecurityNews, Apereo CAS Commit).

Ressources additionnelles

État de correction de la distribution Linux

Disponibilité des correctifs sur les principales distributions Linux et leurs versions.

Debian

Fixe

bookworm

nodejs

Fixe

sid

nodejs

Fixe

trixie

nodejs

Fixe

Ubuntu

Inconnu

bionic (esm-apps)

nodejs

Inconnu

devel

nodejs

Inconnu

focal (esm-apps)

nodejs

Inconnu

jammy

nodejs

Inconnu

jammy (esm-apps)

nodejs

Inconnu

noble

nodejs

Inconnu

noble (esm-apps)

nodejs

Inconnu

resolute

nodejs

Inconnu

Alpine

Fixe

edge

nodejs-current: 26.12.1-r0

Fixe

Source: Ce rapport a été généré à l’aide de l’IA

Apparenté npm Vulnérabilités:

Identifiant CVE

Sévérité

Score

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-106074NONEN/A
  • npm logonpm
  • nodejs
NonOuiOct 23, 2026
CVE-2026-106073NONEN/A
  • npm logonpm
  • nodejs
NonOuiOct 23, 2026
CVE-2026-106072NONEN/A
  • npm logonpm
  • nodejs-full-i18n
NonOuiOct 23, 2026
CVE-2026-106071NONEN/A
  • npm logonpm
  • nodejs24
NonOuiOct 23, 2026
CVE-2026-106070NONEN/A
  • npm logonpm
  • nodejs-full-i18n
NonOuiOct 23, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité dans le cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité pour évaluer votre niveau de risque et identifier les failles dans vos défenses.

Demander une évaluation

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités