November 2026 - CVE Security Bulletin

This November security update covers three denial-of-service CVEs affecting HAProxy Community Edition and HAProxy Enterprise, and the products built on them: HAProxy ALOHA, HAProxy Kubernetes Ingress Controller and HAProxy Unified Gateway for Kubernetes. In each case, a remote, unauthenticated client can send crafted HTTP/2 or HTTP/3 traffic that trips an internal safety check. This stops the HAProxy process and drops every connection it was handling. None of these vulnerabilities expose data or allows code execution. 

Fixed releases of every product are available now, and the latest version includes all three fixes. CVE IDs have been requested, and we will add them to this bulletin once they are assigned.

  • For HTTP/2 (two CVEs, IDs pending)

    • Affected: every HAProxy Community Edition and HAProxy Enterprise branch from 2.6 onward, and the ALOHA, Kubernetes Ingress Controller and Unified Gateway releases built on them.

    • Exposure: any frontend that accepts HTTP/2 from untrusted clients. Update internet-facing instances first.

  • HTTP/3 over QUIC (one CVE, ID pending)

    • Affected: HAProxy Community Edition 3.1 and later, every HAProxy Enterprise branch from 2.6r1 onward, and the ALOHA, Kubernetes Ingress Controller and Unified Gateway releases built on them.

    • Exposure: only instances with a QUIC listener. Instances without one are not affected.

  • End-of-life branches: HAProxy versions based off of 2.7, 2.9 and 3.1 are affected but will not receive fixes. If you run one of these branches, upgrade to a maintained branch.

  • Cloud marketplace images: Updated images are being released on a rolling basis. If you run HAProxy from a marketplace image, update as soon as the new image for your product appears.

See the table below for affected and fixed versions of each product.


CVE

What it affects

Severity

Fixed in

Details

Pending

HAProxy HTTP/2 CONTINUATION frames

7.5 High

See section 1 below

↓

Pending

HAProxy HTTP/2 trailers

7.5 High

Pending

HAProxy HTTP/3 (QUIC) trailers

7.5 High

See section 2 below

↓


1.  HAProxy process stops from crafted HTTP/2 requests (CVE IDs pending)

Severity: 7.5 High (CVSS v3.1) · CWE-617 Reachable Assertion 

Reported by: Yuqi Qiu and Xiang Li, Nankai University AOSP Lab (CONTINUATION frames), and Adam Crawford (trailers)

HTTP/2 CONTINUATION frames: Crafted CONTINUATION frames cause HAProxy to shift buffered data by an amount that is valid, but that an internal safety check wrongly treats as impossible. The check fails and the HAProxy process stops, dropping every connection it was handling.

HTTP/2 trailers: When a request's trailers fill the receive buffer, HAProxy cannot pass them on because part of the buffer is held in reserve, and the stream waits for space that never frees up. A safety check detects this state and stops the process.

Fixed in:

Product

Affected versions

Fixed version

HAProxy Community Edition

2.6, 2.8, 3.0, 3.2, 3.3, 3.4

2.6.36, 2.8.32, 3.0.31, 3.2.27, 3.3.18, 3.4.8

HAProxy Enterprise

2.6r1, 2.8r1, 3.0r1, 3.2r1, 3.3r1, 3.4r1

2.6r1-308.2040, 2.8r1-343.1716, 3.0r1-362.1534, 3.2r1-379.1366, 3.3r1-378.1138, 3.4r1-382.645

HAProxy ALOHA

14.5, 15.5, 16.5, 17.5, 18.0, 18.5

14.5.55, 15.5.54, 16.5.48, 17.5.38, 18.0.17, 18.5.2

HAProxy Community Edition Kubernetes Ingress Controller

v3.2, v3.4

v3.2.20, v3.4.1

HAProxy Enterprise Kubernetes Ingress Controller

v3.2, v3.0, v1.11

v3.2.20-ee1, v3.0.16-ee20, v1.11.15-ee3

HAProxy Unified Gateway for Kubernetes

v1.0, v1.1

v1.0.12, v1.1.2

Recommended action: Update to the fixed build for your branch. If you cannot update right away, turning off HTTP/2 on exposed frontends (removing h2 from the alpn list on bind lines) closes the exposure for both issues.

More detail: CONTINUATION fix commit · trailers fix commit

Our assessment

Both issues affect availability only. None of them exposes data or allows code execution. Each can be triggered from a single unauthenticated connection and stops the whole HAProxy process rather than a single thread An attacker can therefore take an exposed instance down again after every restart. Update promptly, starting with internet-facing instances that accept HTTP/2.


2. HAProxy process stops from HTTP/3 trailers over QUIC (CVE ID pending)

Severity: 7.5 High (CVSS v3.1) · CWE-617 Reachable Assertion 

HTTP/3 trailers: For instances with a QUIC listener configured, the same buffer-reserve condition behind the HTTP/2 trailers issue also exists in HAProxy's HTTP/3 and QUIC layers. When a request whose trailers cannot be passed on trips one of two safety checks, in the HTTP/3 layer or the QUIC multiplexer, the HAProxy process stops.

Fixed in:

Product

Affected versions

Fixed version

HAProxy Community Edition

3.2, 3.3, 3.4

3.2.27, 3.3.18, 3.4.8

HAProxy Enterprise

2.6r1, 2.8r1, 3.0r1, 3.2r1, 3.3r1, 3.4r1

2.6r1-308.2040, 2.8r1-343.1716, 3.0r1-362.1534, 3.2r1-379.1366, 3.3r1-378.1138, 3.4r1-382.645

HAProxy ALOHA

14.5, 15.5, 16.5, 17.5, 18.0, 18.5

14.5.55, 15.5.54, 16.5.48, 17.5.38, 18.0.17, 18.5.2

HAProxy Community Edition Kubernetes Ingress Controller

v3.2, v3.4

v3.2.20, v3.4.1

HAProxy Enterprise Kubernetes Ingress Controller

v3.2, v3.0, v1.11

v3.2.20-ee1, v3.0.16-ee20, v1.11.15-ee3

HAProxy Unified Gateway for Kubernetes

v1.0, v1.1

v1.0.12, v1.1.2

Recommended action: Update to the fixed build for your branch. If you cannot update right away, remove the QUIC listeners (bind lines with quic4@ or quic6@ addresses) and reload HAProxy. This closes the exposure, and clients fall back to HTTP/2 or HTTP/1.1 over TCP.

More detail: HTTP/3 fix commit · QUIC multiplexer fix commit

Our assessment

This issue affects availability only. It does not expose data or allow code execution. QUIC listeners are not enabled by default, so fewer deployments are exposed. Where QUIC is enabled, a single unauthenticated request can stop the process, such instances should be updated promptly.

How to update

Update affected products by pulling the latest image, package or firmware for your branch. If you run an end-of-life branch, upgrade to a maintained branch.

  •  HAProxy Enterprise: see the upgrade instructions in the customer documentation.

  • HAProxy Enterprise with HAProxy Fusion: upgrade your nodes from the Fusion control plane.

  • HAProxy ALOHA: follow the standard firmware update procedure.

  •  HAProxy Community Edition: update to the fixed tagged release, or compile from the latest source.

  • HAProxy Enterprise Kubernetes Ingress Controller: update to the fixed tagged release

  • HAProxy Community Edition Kubernetes Ingress Controller: update to the fixed tagged release

  • HAProxy Unified Gateway for Kubernetes: update to the fixed tagged release

Support

If you are an existing HAProxy customer with questions about these advisories or upgrade procedures, please consult our customer documentation or contact support .

Subscribe to our blog. Get the latest release updates, tutorials, and deep-dives from HAProxy experts.