Quick answers
- Is CVE-2026-55203 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55203 being exploited in the wild.
- How severe is CVE-2026-55203?
- High severity, with a CVSS score of 7.5, published 18 June 2026.
- Which products and versions are affected?
- HAProxy through 3.4.0.
- Is there a fix for CVE-2026-55203?
- A patch was published on 2026-06-18: Fixed in commit 5985276 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55203 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-55203?
- Check whether you run HAProxy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow vulnerability exists in the fcgi_conn structure's drl (demux record length) field in HAProxy through 3.4.0. The field is defined as a uint16_t; when processing a FastCGI record with a contentLength of 65535 and a paddingLength of 1 or more, the addition of these values causes the field to wrap to 0. This leads the state machine to believe a record is complete without consuming the buffer data, causing subsequent data to be misparsed as new FCGI record headers. An attacker controlling a FastCGI backend can exploit this to desynchronize the parser, enabling response smuggling or request routing errors. The issue is fixed by widening the drl field to uint32_t in commit 5985276.
Affected products
- HAProxy HAProxy through 3.4.0
Timeline
- 2026-06-18: disclosed
- 2026-06-18: advisory
- 2026-06-18: patched: Fixed in commit 5985276