An issue was discovered in HAProxy before 3.3.6. The HTTP/3 parser does not check that the received body length matches a previously announced content-length when the stream is closed via a frame with an empty payload. This can cause desynchronization issues with the backend server and could be used for request smuggling. The earliest affected version is 2.6.
References
| Link | Resource |
|---|---|
| https://github.com/haproxy/haproxy/commit/05a295441c621089ffa4318daf0dbca2dd756a84 | Patch |
| https://r3verii.github.io/cve/2026/04/14/haproxy-h3-standalone-fin-smuggling.html | Exploit Third Party Advisory |
| https://www.haproxy.com/documentation/haproxy-aloha/changelog/ | Release Notes |
| https://www.haproxy.org | Product |
| https://www.mail-archive.com/haproxy@formilux.org/msg46752.html | Release Notes |
| https://r3verii.github.io/cve/2026/04/14/haproxy-h3-standalone-fin-smuggling.html | Exploit Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-04-13 17:16
Updated : 2026-06-29 15:28
NVD link : CVE-2026-33555
Mitre link : CVE-2026-33555
CVE.ORG link : CVE-2026-33555
JSON object : View
Products Affected
haproxy
- haproxy
CWE
CWE-130
Improper Handling of Length Parameter Inconsistency
