haproxy: HAProxy 3.2 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (worker-thread CPU exh...
CVE-2026-110353 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-110353, released October 25, 2026. It is not reported as exploited. Patch Radar priority: High.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| haproxy · Debian 14 | 3.2.26-1 | DEBIAN-CVE-2026-110353 | Oct 25, 2026 |
| haproxy · Ubuntu 22.04.1 LTS (jammy) | 2.4.30-0ubuntu0.22.04.3 | haproxy 2.4.30-0ubuntu0.22.04.3 | Nov 4, 2026 |
| haproxy · Ubuntu 24.04.5 LTS (noble) | 2.8.30-0ubuntu0.24.04.2 | haproxy 2.8.30-0ubuntu0.24.04.2 | Nov 4, 2026 |
| haproxy · Ubuntu 26.04.1 LTS (resolute) | 3.2.25-0ubuntu0.26.04.2 | haproxy 3.2.25-0ubuntu0.26.04.2 | Nov 7, 2026 |
| vim-haproxy · Ubuntu 22.04.1 LTS (jammy) | 2.4.30-0ubuntu0.22.04.3 | vim-haproxy 2.4.30-0ubuntu0.22.04.3 | Nov 4, 2026 |
| vim-haproxy · Ubuntu 24.04.5 LTS (noble) | 2.8.30-0ubuntu0.24.04.2 | vim-haproxy 2.8.30-0ubuntu0.24.04.2 | Nov 4, 2026 |
| vim-haproxy · Ubuntu 26.04.1 LTS (resolute) | 3.2.25-0ubuntu0.26.04.2 | vim-haproxy 3.2.25-0ubuntu0.26.04.2 | Nov 7, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.