CVE-2026-110353
Vulnerability record
- High 7.5
Description
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.
Key facts
- Published
- 22 Oct 2026
- Last changed
- 22 Oct 2026
- Assigned by
- mitre
- EPSS
- 0.738% likely to be exploited in the next 30 days, higher than 55.158% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: yes; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 7.5CVSS 3.1, Highfrom the CNA (mitre)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| HAProxy | HAProxy |
|
| HAProxy | HAProxy Enterprise Edition |
|
| HAProxy | Kubernetes Ingress Controller |
|
| Haproxy | Kubernetes Ingress Controller Enterprise |
|
Timeline
- 22 Oct 2026 Published