On this page (7 sections)

On November 18, 2026, the Debian security team published DSA-6638-1, a security update for HAProxy, the load balancing reverse proxy. Debian says several vulnerabilities were found that could result in HTTP request smuggling, request routing errors or denial of service.

If you run HAProxy from Debian 13 (trixie) in front of a website or application, you should plan the update. The advisory is short, so this article also explains what these weakness types mean and how to check your own setup.

What Debian announced

The advisory covers three CVE identifiers in one package update. Debian describes the issues together rather than one by one, and it does not say which CVE maps to which impact. It states that for the stable distribution (trixie), the problems are fixed in version 3.0.11-1+deb13u5, and it recommends upgrading haproxy packages. A Debian bug (1140430) and the Debian security tracker are referenced for detailed status.

Only one publisher, the Debian advisory itself, is available for this story so far. Details such as per-CVE descriptions, severity scores and exploitation status were not in the material we reviewed, so we do not guess at them. Check the security tracker for updates.

What the weakness types mean

The advisory names three outcomes. Which CVE causes which is not specified, so treat these as the range of risk from the update as a whole.

  • HTTP request smuggling: the proxy and the backend server disagree about where one request ends and the next begins. An attacker may be able to slip a request past front-end checks, such as access rules or filtering, or interfere with other users' traffic.
  • Request routing errors: a request may be sent to a backend, or handled under rules, other than the ones you intended. This can matter if you split traffic by host, path or header to separate public and internal services.
  • Denial of service: a crafted request or traffic pattern could make the proxy fail or stop serving. For a load balancer, that can take every site behind it offline.

Because HAProxy usually sits at the edge, flaws here affect everything behind it. That is why even without a published score it is reasonable to patch promptly.

Who is realistically exposed

  • Servers running Debian 13 (trixie) with the distribution's haproxy package installed from Debian repositories.
  • Hosting providers, agencies and businesses that use HAProxy as a reverse proxy, TLS terminator or load balancer in front of web applications.
  • Setups where HAProxy enforces access control or routes between public and internal backends, since smuggling and routing errors matter most there.

The advisory only gives a fixed version for trixie. If you run HAProxy from another source, such as a different distribution, a container image or upstream builds, this advisory does not tell you which version to use. Check that vendor's own notices.

How to check your exposure

This read-only command lists the installed haproxy package version. On trixie you are looking for 3.0.11-1+deb13u5 or newer.

Show the installed haproxy package version (Debian)Shell
dpkg -l haproxy | grep haproxy

This read-only command prints the version of the haproxy binary installed on disk. It does not prove that the running process uses that binary, because a service started before the update keeps running the old one until it is restarted.

Show the installed HAProxy binary versionShell
haproxy -v

To see whether an update is waiting, ask apt for the candidate version. Compare the Candidate line against 3.0.11-1+deb13u5.

Compare installed and candidate versions (Debian)Shell
apt-cache policy haproxy

What to do now

  1. List every host that runs HAProxy, including staging and forgotten load balancers, and note how it was installed.
  2. On Debian trixie, refresh package lists and upgrade the haproxy package to 3.0.11-1+deb13u5 or newer.
  3. Validate your configuration before restarting, then restart or reload HAProxy so the service runs the new binary.
  4. Check the installed version with haproxy -v and confirm with systemctl status that the service shows a start time after the upgrade, then check that your sites respond normally.
  5. Review access logs from before the update for unusual requests, odd status codes or unexpected backend hits.
  6. Subscribe to the debian-security-announce list and watch the Debian security tracker for added details on the three CVEs.

These commands refresh the package index and upgrade only the haproxy package on Debian.

Upgrade only the haproxy package (Debian)Shell
sudo apt update
sudo apt install --only-upgrade haproxy
Caution. Restarting HAProxy can drop active connections. Validate the configuration first and schedule the restart for a quiet period, or use a reload if your setup supports it.

This checks the configuration file for errors without applying it. Run it before restarting; it should report that the configuration is valid.

Validate the HAProxy configuration (run on the server)Shell
haproxy -c -f /etc/haproxy/haproxy.cfg

This restarts the service so it runs the upgraded binary, then shows its status. Look for an active (running) state and a start time that is after your upgrade.

Restart HAProxy and check its status (systemd)Shell
sudo systemctl restart haproxy
sudo systemctl status haproxy

Detection and monitoring afterwards

The advisory contains no indicators of compromise, so there is no specific signature to hunt for. General signals are still worth watching: sudden spikes in 4xx or 5xx responses, requests reaching backends that should be internal only, and unexplained restarts or outages of the proxy.

From the outside, uptime monitoring helps you notice a proxy that has stopped serving, which is the denial of service case. See uptime monitoring explained and Webforta Monitor. For background on filtering at the edge, read what is a WAF. A WAF or monitoring is not a substitute for patching the proxy itself.

What we do not know yet

  • Which CVE corresponds to request smuggling, routing errors or denial of service.
  • CVSS scores or an official severity rating for any of the three CVEs.
  • Whether any of the flaws is being exploited. The advisory does not say.
  • Which upstream HAProxy versions are affected or fixed outside Debian trixie.

We will not fill these gaps with assumptions. If you need certainty for a non-Debian deployment, consult the HAProxy project and your distribution or vendor.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6638-1] haproxy security updatelists.debian.org ·
  • HAProxy
  • Debian
  • DSA
  • Request smuggling
  • Load balancer