CVE-2026-33555

haproxy: HAProxy: Request smuggling via HTTP/3 parser desynchronization

Published Apr 13, 2026 CVSS 3.1 · 4 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A flaw in HAProxy’s HTTP/3 parser fails to verify that the body length announced by the content-length header matches the actual payload length when a stream ends with an empty frame. The mismatch can desynchronize the communication between the proxy and its backend, potentially allowing an attacker to smuggle requests or manipulate request contents. This type of vulnerability is a classic example of data misinterpretation, identified here as CWE‑130.

Affected Systems

All HAProxy installations running any version from 2.6 up to, but not including, 3.3.6 are affected. The problem is confined to the HTTP/3 implementation; systems that do not expose an HTTP/3 receptor to clients are not at risk through this flaw.

Risk and Exploitability

The CVSS score of 4.0 indicates moderate severity, and the absence of an EPSS value means the exact exploit probability cannot be quantified. The vulnerability is not listed in the CISA KEV catalog, suggesting no confirmed exploitation yet. Based on the description, it is inferred that an adversary would need network access to the HAProxy instance’s HTTP/3 interface and the ability to send tailored HTTP/3 frames that terminate a stream with zero payload.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade HAProxy to version 3.3.6 or newer

Generated by OpenCVE AI on April 13, 2026 at 18:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4842-1 haproxy security update
Debian DSA Debian DSA DSA-6291-1 haproxy security update
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title haproxy: HAProxy: Request smuggling via HTTP/3 parser desynchronization
References
Metrics threat_severity

None

threat_severity

Moderate

Type Values Removed Values Added
Description 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.
First Time appeared Haproxy
Haproxy haproxy
Weaknesses CWE-130
CPEs cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*
Vendors & Products Haproxy
Haproxy haproxy
References
Metrics cvssV3_1

{'score': 4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N'}

Weaknesses
  • CWE-130

    Improper Handling of Length Parameter Inconsistency

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Oct 18, 2026, 8:07 PM
Reserved
Mar 22, 2026, 12:00 AM
Status
Modified
Published
Apr 13, 2026, 5:16 PM
Modified
Oct 18, 2026, 8:16 PM
Severity
Moderate
Public date
Apr 13, 2026, 12:00 AM