Vulnerability in Haproxy
CVE-2026-33555
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.0 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N.
EPSS exploit prediction
EPSS 0.003, 25.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Haproxy — versions 2.6
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- r3verii/CVE-2026-33555 (2 stars, last pushed 2026-04-17): One zero-byte QUIC packet is enough to desynchronize HAProxy's backend connection pool and smuggle HTTP requests across unrelated users — even users on a completely different frontend protocol.
References
- www.haproxy.org (Product)
- www.haproxy.com/documentation/haproxy-aloha/changelog/ (Release Notes)
- github.com/haproxy/haproxy/commit/05a295441c621089ffa4318daf0dbca2dd756a84 (Patch)
- www.mail-archive.com/haproxy@formilux.org/msg46752.html (Release Notes)
- r3verii.github.io/cve/2026/04/14/haproxy-h3-standalone-fin-smuggling.html (Exploit, Third Party Advisory)
- lists.debian.org/debian-lts-announce/2026/10/msg00036.html
This CVE has public exploit evidence. See the latest CVEs with public exploits.