cve.bz

CVE-2026-110353 haproxy: Unchecked Return Value

7.5 highEPSS 0.7%

High (7.5) in haproxy. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
HAProxy 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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-252 Unchecked Return Value
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-110353 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110353?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110353?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110353 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • haproxy:haproxy
  • haproxy:haproxy enterprise edition
  • haproxy:kubernetes ingress controller
  • haproxy:kubernetes ingress controller enterprise

Versions

From the CNA's record in the CVE List.

ProductAffected
HAProxyfrom 3.2.0 before 3.2.26
HAProxyfrom 3.3.0 before 3.3.17
HAProxyfrom 3.4.0 before 3.4.6
HAProxyfrom 3.5-dev before 3.5-dev9
HAProxy Enterprise Editionfrom 3.2.0r1 before 3.2r1-378.1259
HAProxy Enterprise Editionfrom 3.3.0r1 before 3.3r1-377.1005
HAProxy Kubernetes Ingress Controllerfrom 3.2.0 before 3.2.17
Haproxy Kubernetes Ingress Controller Enterprisefrom 3.2.0 before 3.2.17-ee1
Haproxy Kubernetes Ingress Controller Enterprisefrom 3.0 before 3.0.16-ee17
Haproxy Kubernetes Ingress Controller Enterprisefrom 1.11 before 1.11.14-ee11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13haproxyno fix listedDEBIAN-CVE-2026-110353
Debian14haproxy3.2.26-1DEBIAN-CVE-2026-110353
Ubuntu20.04:LTS, Pro:16.04:LTS, Pro:18.04:LTShaproxyno fix listedUBUNTU-CVE-2026-110353
Ubuntu22.04:LTShaproxy2.4.30-0ubuntu0.22.04.3UBUNTU-CVE-2026-110353 USN-8972-1
Ubuntu24.04:LTShaproxy2.8.30-0ubuntu0.24.04.2UBUNTU-CVE-2026-110353 USN-8972-1
Ubuntu26.04:LTShaproxy3.2.25-0ubuntu0.26.04.2UBUNTU-CVE-2026-110353 USN-8972-1
Ubuntu26.10haproxy3.4.2-1ubuntu4.1UBUNTU-CVE-2026-110353 USN-8972-1
Red Hathummingbird:1haproxy0:3.0.30-0.1.hum1RHSA-2026:83844
openSUSETumbleweedhaproxy3.4.7+git57.0faeaeda6-2.1openSUSE-SU-2026:12431-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important severity because an unauthenticated remote attacker can cause high CPU exhaustion across worker threads without requiring special privileges or user interaction. When HAProxy operates as a public-facing load balancer or reverse proxy handling untrusted traffic over HTTP/2, repeated malformed frames can monopolize worker capacity until request timeouts terminate the session. Deployments that do not enable HTTP/2 negotiation or that restrict listener access to trusted networks face significantly reduced risk.

ProductPackageStateAdvisory
Red Hat Hardened Imageshaproxy-main-3.0.30-0.1.hum1Fixed 2026-10-16RHSA-2026:83844
Red Hat Ceph Storage 5haproxyFix deferred
Red Hat Enterprise Linux 10haproxyAffected
Red Hat Enterprise Linux 7haproxyAffected
Red Hat Enterprise Linux 8haproxyAffected
Red Hat Enterprise Linux 9haproxyAffected
Red Hat OpenShift Container Platform 4haproxyAffected
Red Hat OpenShift Container Platform 5haproxyAffected
Red Hat OpenShift Container Platform 5haproxy32Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-110353.

References

Check your stackJSON