Security advisory Debian

HAProxy on Debian, Oct 2025 to Oct 2026: DSA-6570-1, DLA-4842-1 and earlier denial-of-service fixes

Five Debian advisories in a year fixed HAProxy DoS and HTTP/3 request smuggling bugs. The versions to run now on Debian 12 and 13, and how to check.

Published
Reading time
4 min read

Security advisory Vulnerability

Severity: High Status: Patched
Status
Fixed versions are available for Debian 13 (trixie) and Debian 12 (bookworm).
Affected
  • haproxy in Debian 13 (trixie) before 3.0.11-1+deb13u4
  • haproxy in Debian 12 (bookworm) before 2.6.12-1+deb12u4
  • haproxy in Debian 13 (trixie) before 3.0.11-1+deb13u3
  • haproxy in Debian 13 (trixie) before 3.0.11-1+deb13u2
  • haproxy in Debian 13 (trixie) before 3.0.11-1+deb13u1
  • haproxy in Debian 12 (bookworm) before 2.6.12-1+deb12u3
Published
Updated

What you should do

  • Upgrade to 3.0.11-1+deb13u4 on Debian 13 or 2.6.12-1+deb12u4 on Debian 12.
  • Check the configuration with haproxy -c, then restart HAProxy node by node.
  • Disable QUIC and HTTP/3 listeners you do not need.
  • Monitor CPU per HAProxy thread so a stuck worker shows up quickly.
Timeline
  1. Debian published DSA-6017-1 for haproxy.
  2. Debian published DSA-6130-1 for haproxy.
  3. Debian published DSA-6291-1 for haproxy.
  4. Debian published DSA-6570-1 for haproxy.
  5. The Debian LTS team published DLA-4842-1 for haproxy.
  6. Skyline published this summary.

HAProxy sits in front of many web applications, so a bug that makes it spin or crash takes everything behind it down. Between October 2025 and October 2026 Debian published five HAProxy advisories, the latest being DSA-6570-1 for Debian 13 (trixie) and DLA-4842-1 for Debian 12 (bookworm), both on 18 October 2026. Most fix denial of service; one fixes HTTP request smuggling over HTTP/3. Each package includes the earlier fixes.

At a glance

ReleaseInstall at leastLatest advisory
Debian 13 (trixie)3.0.11-1+deb13u4DSA-6570-1 (18 Oct 2026)
Debian 12 (bookworm)2.6.12-1+deb12u4DLA-4842-1 (18 Oct 2026)

Severity: High, based on CVE-2026-110354 and CVE-2025-11230, both CVSS 3.1 7.5 (remote, unauthenticated denial of service) from their CNAs. None of these CVEs is in CISA's Known Exploited Vulnerabilities catalog (30 Oct 2026).

The advisories

AdvisoryDateIssueReleases
DSA-6017-13 Oct 2025CVE-2025-11230: denial of service when parsing JSON numbersbookworm, trixie
DSA-6130-112 Feb 2026CVE-2026-26081: crash from a crafted QUIC INITIAL packettrixie
DSA-6291-122 May 2026CVE-2026-33555: HTTP/3 request smugglingtrixie
DSA-6570-118 Oct 2026Two denial-of-service issues, now tracked as CVE-2026-110354trixie
DLA-4842-118 Oct 2026CVE-2026-33555 and the October denial-of-service issuesbookworm

What the vulnerabilities are

  • CVE-2025-11230 (JSON). Inefficient parsing of crafted JSON numbers in the bundled mjson code lets a remote attacker exhaust CPU. It matters if your configuration uses HAProxy's JSON converters on request data.
  • CVE-2026-110354 (HTTP/1.1 chunked). The CVE record describes a remote, unauthenticated attacker causing persistent CPU exhaustion of a worker thread with a crafted chunked request. When Debian published DSA-6570-1 the CVE IDs were not yet available; the tracker has since attached this one.
  • CVE-2026-26081 (QUIC). HAProxy's own news says a specially crafted QUIC packet could crash the process in 3.0 and later; the tracker marks bookworm's 2.6 as not affected.
  • CVE-2026-33555 (HTTP/3). The HTTP/3 parser did not check that the body length matched the announced Content-Length, which may allow request smuggling against the backend. Debian notes that these features are not enabled by default in bookworm's packages.

The QUIC and HTTP/3 issues only reach you if you configured QUIC listeners. Check with:

grep -nE 'quic|alpn h3' /etc/haproxy/haproxy.cfg

Are you affected?

apt policy haproxy
haproxy -v

Compare the Installed line with the table. haproxy -v shows the upstream version (3.0.11 or 2.6.12) and does not change with Debian's patches, so rely on apt policy. If you run HAProxy from another repository or a container image, check that source's advisories instead.

How to update

sudo apt update
sudo apt install --only-upgrade haproxy

Before restarting, validate the configuration with the new binary:

sudo haproxy -c -f /etc/haproxy/haproxy.cfg

Restart or reboot?

No reboot. Make sure the running process is the new one: if systemctl show -p ActiveEnterTimestamp haproxy is older than the upgrade, restart it in a quiet period, because a restart drops open connections:

sudo systemctl restart haproxy

With several load balancers, update and restart them one at a time.

Still open

On 31 October 2026 the tracker listed a few further HAProxy CVEs as open with no DSA planned for now, for example CVE-2026-55203 in FastCGI record parsing (relevant if you use FastCGI backends) and CVE-2026-55204 in HTTP/2 header compression. Keep an eye on the page, and keep request limits and timeouts (timeout http-request, maxconn) set so a single client cannot tie up the proxy.

Sources

SKYLINE Engineering

@skyline

The engineering team at SKYLINE Industrial Solutions. We publish field-tested guides drawn from real KSA and GCC deployments.

See author profile
SKYLINE engineering services

Need this implemented for you?

Reading is free — building it right takes a team. SKYLINE engineers ship Debian for Aramco vendors, banks, hospitals and government agencies across Saudi Arabia. Talk to us before you start.

Aramco Approved Contractor ISO 9001 · ISO 27001 SAMA CSF aligned NCA ECC ready 247+ KSA clients

Comments

0 total · 0 threads
Be the first to leave a comment.