Live › vulnerability › CVE-2026-110353
Go to dashboardHAProxy 3.2 before 3.4.6 does not check for short reads in its HTTP/2 PING frame handler, so a truncated PING leaves data unconsumed and the multiplexer tasklet spins. An unauthenticated remote attacker opening many such connections can exhaust worker-thread CPU and deny service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
HAProxy 3.2 releases before 3.4.6 that accept HTTP/2 connections from the internet or an untrusted network are exposed, since the attack needs no credentials. Deployments that do not serve HTTP/2 on a bind line, or that run a different HAProxy line, are not described as affected by the sources.
No product ranges from the sources yet.
haproxy -v and check whether the version is 3.2.x below 3.4.6.proto h2 or alpn h2 in the bind line of haproxy.cfg).3.4.6 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-110353")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.