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.
Metrics
Affected Vendors & Products
References
History
Mon, 14 Sep 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 14 Sep 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | HTTP/3 Request Smuggling Exploit via Chunk Length Mismatch in HAProxy | haproxy: HAProxy: HTTP Request Smuggling via HTTP/3 Multiplexer Desynchronization |
| Weaknesses | CWE-444 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 14 Sep 2026 06:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | HTTP/3 Request Smuggling Exploit via Chunk Length Mismatch in HAProxy |
Sun, 13 Sep 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | HTTP/3 Request Smuggling via Chunked Transfer Coding in HAProxy |
Sun, 13 Sep 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Haproxy
Haproxy haproxy |
|
| Vendors & Products |
Haproxy
Haproxy haproxy |
Sun, 13 Sep 2026 12:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | HTTP/3 Request Smuggling via Chunked Transfer Coding in HAProxy |
Sun, 13 Sep 2026 04:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Weaknesses | CWE-130 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: mitre
Published: 2026-09-13T03:37:55.854Z
Updated: 2026-09-14T15:48:00.475Z
Reserved: 2026-09-13T03:37:55.518Z
Link: CVE-2026-90678
Updated: 2026-09-14T15:47:56.554Z
Status : Awaiting Analysis
Published: 2026-09-13T04:17:25.227
Modified: 2026-09-22T19:56:19.073
Link: CVE-2026-90678