llamaCVEVulnerability Intelligence
/
HAProxy

CVE-2026-90678

An issue was discovered in HAProxy 3.3.0 through 3.4.4 and in 3.5-dev1 through 3.5-dev5

Sin parche publicadolength check flaw
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:L Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición67 dDesde la divulgación, 12 sept 2026, 10:37 p. m.
Detección65 dDesde 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. No hay versión corregida: aplique mitigaciones.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada
13 sept 26
14 sept 26
17 nov 26
19 nov 26
13 sept 26
30 sept 26
16 oct 26
2 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-90678 divulgada · CVSS 7.5 (CNA)
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen

An issue was discovered in HAProxy 3.3.0 through 3.4.4 and in 3.5-dev1 through 3.5-dev5. Exploitation requires an HTTP/3 frontend: HAProxy must be built with QUIC support and configured with a QUIC bind listener, and the affected traffic must reach a backend over HTTP/1.1 using chunked transfer coding on a reused connection. Under those conditions, when an HTTP/3 request carries no Content-Length header, the HTTP/3 multiplexer credits the length declared in a DATA frame header to the stream endpoint's known-input-payload estimate at the moment the frame header is decoded, before the payload has been received, and that declared length is emitted verbatim as the HTTP/1.1 chunk size. A remote unauthenticated client that declares more payload than it delivers and then ends the stream causes HAProxy to announce a chunk larger than the bytes it writes and to return the connection to the idle pool in a desynchronized state. The result is potential HTTP request smuggling on reused backend connections: an attacker can place a request past a frontend rule such as a path-based http-request deny, so that the smuggled request is never seen by HAProxy's HTTP analysis, and can cause concurrent clients' requests, including their request lines and Authorization headers, to be consumed as the attacker's request body and lost. Exploitation is not deterministic; it depends on a race with backend connection pooling, succeeding in a majority of but not all trials during testing, and can be retried freely. The mechanism was introduced in 3.3-dev10; releases 3.2.x and earlier are unaffected.

Vector CVSS 3.1

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:N
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:L
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
HAProxy≥ 3.3.0 ≤ 3.3.14
HAProxy≥ 3.4.0 ≤ 3.4.4
HAProxy≥ 3.5-dev1 ≤ 3.5-dev5
3.3.0
3.3.14
3.4.0
3.4.4
3.5-dev1
3.5-dev5
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
HAProxy
Sin parche — — —
Explotación

Arsenal público

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

Registro
EscenarioGENERALmitre
configurationOnly deployments with an HTTP/3 frontend are affected. This requires HAProxy built with USE_QUIC=1 and at least one QUIC bind listener in a frontend; no experimental directives are needed to enable it. The affected code path is reached when such a request carries no Content-Length header and is forwarded to a backend over HTTP/1.1 with chunked transfer coding. Deployments without a QUIC listener are not exposed.mitre
MitigaciónRemoving the QUIC bind listeners from all frontends eliminates exposure, since an HTTP/3 frontend is required. Releases in the 3.2 branch and earlier do not contain the mechanism.mitre
solutionUpgrade to a release or backported Enterprise version containing fix ("BUG/MAJOR: h3: reject H3 truncated frames"), first shipped in 3.5-dev6.mitre
Referencias
Fabricantehttp://git.haproxy.org/?p=haproxy.git;a=commit;h=86a4ebc761a278838e8cb06f3a292282ba704c65
Fabricantehttps://www.haproxy.org/download/3.5/src/CHANGELOG
Parchehttps://github.com/haproxy/haproxy/commit/86a4ebc761a278838e8cb06f3a292282ba704c65

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