CVE-2026-33555·HAProxy vulnerability
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.
- Severity
- medium
- Software
- HAProxy
- Fixed in
- 3.3.6
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.58% — higher than 46% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 2.6.0
Until: 3.3.6
Fixed in: 3.3.6
How to fix this CVE
Update HAProxy to version 3.3.6 or later to resolve a critical HTTP/3 parsing vulnerability that can lead to request smuggling attacks. The vulnerability occurs when HAProxy fails to validate that received HTTP/3 body lengths match the announced content-length header, potentially allowing attackers to desynchronize backend servers. Immediately patch all HAProxy instances running versions 2.6.0 through 3.3.5 in your environment.
sudo dnf check-update haproxy && sudo dnf update haproxyDefensia detects this vulnerability
How to check if you are affected
- Check the installed HAProxy version: haproxy -v | grep version
- Verify if HTTP/3 support is enabled in your HAProxy configuration: grep -i 'quic\|h3' /etc/haproxy/haproxy.cfg
- Search HAProxy logs for malformed HTTP/3 streams with content-length mismatches: grep -i 'content-length' /var/log/haproxy.log | grep -i 'mismatch\|fin\|stream'
- Confirm patch installation by checking the version is 3.3.6 or higher: haproxy -v && haproxy -c -f /etc/haproxy/haproxy.cfg
FAQ
What is CVE-2026-33555?
CVE-2026-33555 is an HTTP/3 protocol parsing defect in HAProxy where the proxy fails to enforce content-length validation when HTTP/3 streams terminate with empty-payload frames. This mismatch can be weaponized for request smuggling, allowing attackers to inject unauthorized requests that bypass security controls.
Is CVE-2026-33555 being actively exploited?
No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploit code is available. However, the proof-of-concept research has been documented, so organizations should prioritize patching to prevent future exploitation.
What versions of HAProxy are affected by CVE-2026-33555?
HAProxy versions 2.6.0 through 3.3.5 are vulnerable. Version 3.3.6 and later contain the fix and should be deployed immediately.
How do I check if my server is vulnerable to CVE-2026-33555?
Run 'haproxy -v' to check your version. If it is 2.6.0 or later but earlier than 3.3.6, and HTTP/3 is enabled in your configuration, your instance is vulnerable.
Does Defensia detect CVE-2026-33555?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If HAProxy is installed on a monitored server, CVE-2026-33555 will appear in your dashboard with remediation steps.
Related HAProxy CVEs
References
- https://github.com/haproxy/haproxy/commit/05a295441c621089ffa4318daf0dbca2dd756a84
- https://r3verii.github.io/cve/2026/04/14/haproxy-h3-standalone-fin-smuggling.html
- https://www.haproxy.com/documentation/haproxy-aloha/changelog/
- https://www.haproxy.org
- https://www.mail-archive.com/haproxy@formilux.org/msg46752.html
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-33555. Free for 1 server.
Get started free