llamaCVEVulnerability Intelligence
/
Node.js

CVE-2026-123864

Node.js cross-connection memory leak in HTTPS request parser

A remote client without credentials can read TLS private keys and other users' requests from HTTPS servers.

UnclearParche disponibleuse-after-free
Descargar PNG JSON
CVSS 3.0
8.1
Alta
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versiones22.23.5 · 24.22.3 · 26.13.1
Exposición8 dDesde la divulgación, 11 nov 2026, 1:17 p. m.
Detección8 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, no automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada +2
Verificada
11 nov 26
16 nov 26
20 nov 26
11 nov 26
14 nov 26
16 nov 26
18 nov 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-123864 divulgada · CVSS 8.1 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Fuente: ENISA EUVD Registro visto por primera vez en ENISA EUVD
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 11 nov 2026

Node.js HTTPS servers can leak memory from other connections, including TLS private keys and other users' requests, to an unauthenticated remote client. The attacker must send a request to a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and the leak only works when the server echoes or stores request bodies on an ordinary route; cleartext node:http is not affected.

Affects Node.js 22.x, 24.x and 26.x HTTPS servers whose handlers flush headers before the request body ends and echo or store request bodies. Fixed in 22.23.5, 24.22.3 and 26.13.1.

¿Qué significa?A flaw in the HTTPS request parser's TLS write handling lets an unauthenticated client read memory belonging to other connections, which can include TLS private keys and other users' requests.
¿Quién está afectado?Only HTTPS servers on the Node.js 22.x, 24.x and 26.x release lines are in scope; cleartext node:http is not affected. The setup also needs a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, plus a route that echoes or stores request bodies. Node.js version can be checked with node --version, and server code can be searched for flushHeaders calls.
¿Qué hacer?Upgrade to the fixed version for the release line in use: 22.23.5, 24.22.3 or 26.13.1.
Descripción original del registro (openjs)

A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Node.js HTTPS server whose handler calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk“requires a handler that calls res.flushHeaders() before the request body ends”
02
A route that echoes or stores a request body, to read the leaked memory“requires any ordinary route that echoes or stores a request body”
03
Cleartext node:http is not affected, so the HTTPS server is required“node:http is not affected.”
04
Node.js 22.x, 24.x or 26.x release lines“This vulnerability affects all users in active release lines: 22.x, 24.x, 26.x”
¿Quién debe revisar?Teams running Node.js 22.x, 24.x or 26.x HTTPS servers (node:https) whose handlers call res.flushHeaders() before the request body ends, or that echo or store request bodies.
Vector CVSS 3.0

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:L
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
node≥ 0.0.0 < 22.23.5
node≥ 23.0.0 < 24.22.3
node≥ 25.0.0 < 26.13.1
0.0.0
22.23.5
23.0.0
24.22.3
25.0.0
26.13.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
node
Corregida 22.23.5, 24.22.3, 26.13.1 — —
Versiones corregidas22.23.524.22.326.13.1
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://nodejs.org/en/blog/vulnerability/november-2026-security-releases
Otrahttps://cna.openjsf.org/security-advisories.html

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.