Aller au contenu
en Se connecter
3.7 Faible

CVE-2026-58044 A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild…

Description

A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from the visible `IncomingMessage` headers while piping the original body to a reused backend connection. Node.js can omit headers beyond `maxHeadersCount` / `maxHeaderPairs` from `req.headers`, `req.rawHeaders`, and `req.headersDistinct`, while still using those omitted headers internally for HTTP message framing. In particular, `Content-Length` can be hidden from userland while the request body is still delivered. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

Produits et versions touchés

Produit Versions touchées Corrigé en
Node 26.5.0 Pas de correctif indiqué
Node 24.18.0 Pas de correctif indiqué
Node 22.23.1 Pas de correctif indiqué

Références

Chronologie

  1. Publiée
  2. Dernière modification

Autres CVE de Node

Les 129 CVE de Node →
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… 3.7 Faible CVE-2026-106069 A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP… 7.4 Élevée CVE-2026-106074 A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`,… 4.8 Moyenne CVE-2026-105483 A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a… 7.4 Élevée
Suivre cette CVE