Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

HAProxy · Vulnerability

CVSS 3.1 7.5 HIGHCheck source for fixed versionsKEV status unknown

cve-program · CVE-2026-90678

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-90678

Published

HAProxy

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "defaultStatus": "unaffected",
                    "modules": [
                        "HTTP/3 multiplexer",
                        "HTTP/1 multiplexer"
                    ],
                    "product": "HAProxy",
                    "programFiles": [
                        "src/h3.c",
                        "src/mux_h1.c"
                    ],
                    "programRoutines": [
                        {
                            "name": "h3_rcv_buf"
                        }
                    ],
                    "vendor": "HAProxy",
                    "versions": [
                        {
                            "lessThanOrEqual": "3.3.14",
                            "status": "affected",
                            "version": "3.3.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThanOrEqual": "3.4.4",
                            "status": "affected",
                            "version": "3.4.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThanOrEqual": "3.5-dev5",
                            "status": "affected",
                            "version": "3.5-dev1",
                            "versionType": "custom"
                        },
                        {
                            "status": "unaffected",
                            "version": "3.5-dev6",
                            "versionType": "custom"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 16:22 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current