CVE-2026-90678 (GCVE-0-2026-90678)
Vulnerability from cvelistv5 – Published: 2026-09-13 03:37 – Updated: 2026-09-14 15:48
VLAI
EPSS
VEX
Summary
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.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-09-14 15:47 UTC
CWE
- CWE-130 - Improper Handling of Length Parameter Inconsistency
Assigner
References
3 references
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-90678",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-09-14T15:47:26.078603Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-09-14T15:48:00.475Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"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"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eOnly 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.\u003c/p\u003e"
}
],
"value": "Only 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."
}
],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s 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\u0027s HTTP analysis, and can cause concurrent clients\u0027 requests, including their request lines and Authorization headers, to be consumed as the attacker\u0027s 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": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:L",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-130",
"description": "CWE-130 Improper Handling of Length Parameter Inconsistency",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-09-13T03:37:55.854Z",
"orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
"shortName": "mitre"
},
"references": [
{
"name": "BUG/MAJOR: h3: reject H3 truncated frames",
"tags": [
"patch"
],
"url": "https://github.com/haproxy/haproxy/commit/86a4ebc761a278838e8cb06f3a292282ba704c65"
},
{
"tags": [
"patch"
],
"url": "http://git.haproxy.org/?p=haproxy.git;a=commit;h=86a4ebc761a278838e8cb06f3a292282ba704c65"
},
{
"name": "HAProxy 3.5-dev6 ChangeLog",
"tags": [
"release-notes"
],
"url": "https://www.haproxy.org/download/3.5/src/CHANGELOG"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade to a release or backported Enterprise version containing fix (\"BUG/MAJOR: h3: reject H3 truncated frames\"), first shipped in 3.5-dev6.\u003c/p\u003e"
}
],
"value": "Upgrade to a release or backported Enterprise version containing fix (\"BUG/MAJOR: h3: reject H3 truncated frames\"), first shipped in 3.5-dev6."
}
],
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eRemoving 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.\u003c/p\u003e"
}
],
"value": "Removing 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."
}
],
"x_generator": {
"engine": "CVE-Request-form 0.0.1"
}
}
},
"cveMetadata": {
"assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
"assignerShortName": "mitre",
"cveId": "CVE-2026-90678",
"datePublished": "2026-09-13T03:37:55.854Z",
"dateReserved": "2026-09-13T03:37:55.518Z",
"dateUpdated": "2026-09-14T15:48:00.475Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-90678",
"date": "2026-09-14",
"epss": "0.0052",
"percentile": "0.42646"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-90678\",\"sourceIdentifier\":\"cve@mitre.org\",\"published\":\"2026-09-13T04:17:25.227\",\"lastModified\":\"2026-09-14T16:17:36.723\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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\u0027s 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\u0027s HTTP analysis, and can cause concurrent clients\u0027 requests, including their request lines and Authorization headers, to be consumed as the attacker\u0027s 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.\"}],\"affected\":[{\"source\":\"cve@mitre.org\",\"affectedData\":[{\"vendor\":\"HAProxy\",\"product\":\"HAProxy\",\"defaultStatus\":\"unaffected\",\"modules\":[\"HTTP/3 multiplexer\",\"HTTP/1 multiplexer\"],\"programFiles\":[\"src/h3.c\",\"src/mux_h1.c\"],\"programRoutines\":[{\"name\":\"h3_rcv_buf\"}],\"versions\":[{\"version\":\"3.3.0\",\"lessThanOrEqual\":\"3.3.14\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"3.4.0\",\"lessThanOrEqual\":\"3.4.4\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"3.5-dev1\",\"lessThanOrEqual\":\"3.5-dev5\",\"versionType\":\"custom\",\"status\":\"affected\"},{\"version\":\"3.5-dev6\",\"versionType\":\"custom\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"cve@mitre.org\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:L\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":2.2,\"impactScore\":4.7}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-09-14T15:47:26.078603Z\",\"id\":\"CVE-2026-90678\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"cve@mitre.org\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-130\"}]}],\"references\":[{\"url\":\"http://git.haproxy.org/?p=haproxy.git;a=commit;h=86a4ebc761a278838e8cb06f3a292282ba704c65\",\"source\":\"cve@mitre.org\"},{\"url\":\"https://github.com/haproxy/haproxy/commit/86a4ebc761a278838e8cb06f3a292282ba704c65\",\"source\":\"cve@mitre.org\"},{\"url\":\"https://www.haproxy.org/download/3.5/src/CHANGELOG\",\"source\":\"cve@mitre.org\"}]}}",
"redhat_vex": {
"aggregate_severity": "Important",
"current_release_date": "2026-09-14T10:29:59+00:00",
"cve": "CVE-2026-90678",
"id": "CVE-2026-90678",
"initial_release_date": "2026-09-13T03:37:55.854000+00:00",
"product_status:known_affected": "1",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "haproxy: HAProxy: HTTP Request Smuggling via HTTP/3 Multiplexer Desynchronization",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-90678.json",
"version": "3"
},
"vulnrichment": {
"containers": "{\"cna\": {\"affected\": [{\"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\"}]}], \"configurations\": [{\"lang\": \"en\", \"supportingMedia\": [{\"base64\": false, \"type\": \"text/html\", \"value\": \"\u003cp\u003eOnly 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.\u003c/p\u003e\"}], \"value\": \"Only 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.\"}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"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\u0027s 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\u0027s HTTP analysis, and can cause concurrent clients\u0027 requests, including their request lines and Authorization headers, to be consumed as the attacker\u0027s 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\": [{\"cvssV3_1\": {\"attackComplexity\": \"HIGH\", \"attackVector\": \"NETWORK\", \"availabilityImpact\": \"LOW\", \"baseScore\": 7.5, \"baseSeverity\": \"HIGH\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"HIGH\", \"privilegesRequired\": \"NONE\", \"scope\": \"CHANGED\", \"userInteraction\": \"NONE\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:L\", \"version\": \"3.1\"}, \"format\": \"CVSS\", \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"problemTypes\": [{\"descriptions\": [{\"cweId\": \"CWE-130\", \"description\": \"CWE-130 Improper Handling of Length Parameter Inconsistency\", \"lang\": \"en\", \"type\": \"CWE\"}]}], \"providerMetadata\": {\"orgId\": \"8254265b-2729-46b6-b9e3-3dfca2d5bfca\", \"shortName\": \"mitre\", \"dateUpdated\": \"2026-09-13T03:37:55.854Z\"}, \"references\": [{\"name\": \"BUG/MAJOR: h3: reject H3 truncated frames\", \"tags\": [\"patch\"], \"url\": \"https://github.com/haproxy/haproxy/commit/86a4ebc761a278838e8cb06f3a292282ba704c65\"}, {\"tags\": [\"patch\"], \"url\": \"http://git.haproxy.org/?p=haproxy.git;a=commit;h=86a4ebc761a278838e8cb06f3a292282ba704c65\"}, {\"name\": \"HAProxy 3.5-dev6 ChangeLog\", \"tags\": [\"release-notes\"], \"url\": \"https://www.haproxy.org/download/3.5/src/CHANGELOG\"}], \"solutions\": [{\"lang\": \"en\", \"supportingMedia\": [{\"base64\": false, \"type\": \"text/html\", \"value\": \"\u003cp\u003eUpgrade to a release or backported Enterprise version containing fix (\\\"BUG/MAJOR: h3: reject H3 truncated frames\\\"), first shipped in 3.5-dev6.\u003c/p\u003e\"}], \"value\": \"Upgrade to a release or backported Enterprise version containing fix (\\\"BUG/MAJOR: h3: reject H3 truncated frames\\\"), first shipped in 3.5-dev6.\"}], \"workarounds\": [{\"lang\": \"en\", \"supportingMedia\": [{\"base64\": false, \"type\": \"text/html\", \"value\": \"\u003cp\u003eRemoving 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.\u003c/p\u003e\"}], \"value\": \"Removing 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.\"}], \"x_generator\": {\"engine\": \"CVE-Request-form 0.0.1\"}}, \"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-90678\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-09-14T15:47:26.078603Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-09-14T15:47:56.554Z\"}}]}",
"cveMetadata": "{\"cveId\": \"CVE-2026-90678\", \"assignerOrgId\": \"8254265b-2729-46b6-b9e3-3dfca2d5bfca\", \"state\": \"PUBLISHED\", \"assignerShortName\": \"mitre\", \"dateReserved\": \"2026-09-13T03:37:55.518Z\", \"datePublished\": \"2026-09-13T03:37:55.854Z\", \"dateUpdated\": \"2026-09-14T15:48:00.475Z\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…