llamaCVEVulnerability Intelligence
/
OpenSSL

CVE-2026-124709

OpenSSL memory leak in QUIC server for rejected streams

A remote client can repeatedly open and reset streams to exhaust server memory and drop connections.

Afecta la configuración por defectoParche disponiblememory leak
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Fuente: CISA-ADP
ExplotaciónSin evidenciaSSVC: ninguna · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versiones3.5.10 · 4.0.4 · 4.1.1
Exposición4 dDesde la divulgación, 17 nov 2026, 3:14 a. m.
Detección15 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Agéndala y deja de pensar en ella.No corre prisa, pero no la pierdas de vista.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +2
Explotación
Remediación
Monitoreo
Detectada +2
Verificada
17 nov 26
18 nov 26
21 nov 26
17 nov 26
18 nov 26
19 nov 26
20 nov 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-124709 divulgada · CVSS 7.5 (CISA-ADP)
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 · 17 nov 2026

OpenSSL's QUIC server keeps state for rejected streams when the peer resets them before the rejection is signalled. A remote client that completes the QUIC handshake can repeatedly open and reset streams, growing server memory until the process runs out of memory and its connections are lost.

Affects OpenSSL 3.5.0 to 3.5.10, 4.0.0 to 4.0.4 and 4.1.0 QUIC servers with a default stream and rejected incoming streams. Fixed in 3.5.10, 4.0.4 and 4.1.1.

¿Qué significa?When a QUIC server rejects a stream the application does not accept, a peer that resets that stream before the rejection is signalled can cause the server to keep memory it should release. When the peer keeps opening and resetting streams, server memory grows without bound until the process runs out of memory, which drops every connection on that server (Denial of Service).
¿Quién está afectado?Affected are OpenSSL 3.5.0 to 3.5.10, 4.0.0 to 4.0.4 and 4.1.0. The server must have a default stream, meaning the application has read from or written to the connection, and its incoming stream policy must reject streams the application does not accept, which is the default behaviour or the REJECT policy set explicitly. To check a version, run the openssl version command.
¿Qué hacer?The vendor says OpenSSL 4.1 users should upgrade to OpenSSL 4.1.1. The fixed releases for the other affected branches are 4.0.4 and 3.5.10.
Descripción original del registro (openssl)

Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Server has a default stream, meaning the application has read from or written to the connection“meaning the application has read from or written to the connection”
02
Incoming stream policy rejects streams the application does not accept (default behaviour, or the REJECT policy set explicitly)“the effective incoming stream policy rejects streams”
03
Peer resets the stream before the rejection is signalled“the reset cancels the pending STOP_SENDING”
04
Peer keeps the connection open and repeatedly opens and resets streams“keeps opening and resetting streams”
¿Quién debe revisar?Teams running OpenSSL 4.1, 4.0 or 3.5 QUIC servers, including default-configured servers that use a default stream
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CISA-ADP
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:N
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
10.0/ 10Muy alto
Vector 10.0 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida
OpenSSL≥ 3.5.0 < 3.5.10
OpenSSL≥ 4.0.0 < 4.0.4
OpenSSL≥ 4.1.0 < 4.1.1
3.5.0
3.5.10
4.0.0
4.0.4
4.1.0
4.1.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
OpenSSL
Corregida 3.5.10, 4.0.4, 4.1.1 — —
Versiones corregidas3.5.104.0.44.1.1
Explotación

Arsenal público

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

Referencias
Fabricantehttps://openssl-library.org/news/secadv/20261117.txt
Parchehttps://github.com/openssl/openssl/commit/ead311df1037e7994a6d86c7e862d71ad59c52c7
Parchehttps://github.com/openssl/openssl/commit/22291a6af12f158fbb13bfbd572a33dbdbf290d2
Parchehttps://github.com/openssl/openssl/commit/f3acb0a3328046741479482c51cec815839e1b05

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