medium CVSS 4 EPSS 0.58%

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 haproxy

Defensia detects this vulnerability

How to check if you are affected

  1. Check the installed HAProxy version: haproxy -v | grep version
  2. Verify if HTTP/3 support is enabled in your HAProxy configuration: grep -i 'quic\|h3' /etc/haproxy/haproxy.cfg
  3. 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'
  4. 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

CVE-2026-55203CVSS 7.5HAProxy through 3.4.0, fixed in commit 5985276, contains an integer overflow vulnerability in the fcgi_conn structure's drl field that allows buffer misparse as new FCGI record headers. When contentLength is 65535 and paddingLength is 1 or more, the drl field wraps to 0, causing incorrect record consumption and allowing malicious FastCGI backends to desynchronize the FCGI framing parser, potentially causing request routing errors, response smuggling, or memory safety issues.
CVE-2026-55204CVSS 7.5HAProxy through 3.4.0, fixed in commit 9a6d1fe, contains a null pointer dereference vulnerability in hpack_dht_insert() within src/hpack-tbl.c that fails to validate the return value of hpack_dht_defrag() when the memory pool is exhausted. An attacker can trigger HPACK dynamic table insertions under memory pressure to dereference a NULL pointer and crash HAProxy worker processes, causing denial of service.
CVE-2026-110353CVSS 7.5HAProxy 3.2 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (worker-thread CPU exhaustion) via a truncated HTTP/2 PING frame. h2c_handle_ping in src/mux_h2.c does not check for a short read, unlike the other H2 frame handlers. Because the incomplete frame cannot be processed, its data is never consumed, and the H2 multiplexer tasklet is repeatedly woken by that pending data without making progress. The CPU spins until timeout http-request closes the connection, and an attacker opening many such connections can sustain high CPU usage.
CVE-2026-110354CVSS 7.5HAProxy 3 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (persistent worker-thread CPU exhaustion) via an HTTP/1.1 chunked request. Although the H1 multiplexer drains the request before closing the stream, the parser repeatedly re-processes the same bytes without making progress. The affected thread stays busy at 100% CPU after timeouts expire and after the client disconnects, and repeated requests can consume all worker threads until the process is restarted.
CVE-2026-26081CVSS 4.8HAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format. HAProxy Enterprise and ALOHA are also affected.

References

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