# CVE-2026-26080: HAProxy Community Edition 3.2.x through 3.3.x before 3.3.3 can enter a loop or crash because varint is mishandled. HAProxy Enterprise and ALOHA are also affected.

CVE-2026-26080 is fixed in haproxy on 1 platform, first by OPENSUSE-SU-2026:20290-1, released February 27, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-26080
- Priority: Routine
- CVSS: 3.7 (Low)
- EPSS: 0.0055
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Feb 27, 2026
- Weakness: Unchecked Return Value
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26080

## Description

HAProxy Community Edition 3.2.x through 3.3.x before 3.3.3 can enter a loop or crash because varint is mishandled. HAProxy Enterprise and ALOHA are also affected.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | haproxy Debian 14 | 3.2.11-2 | [DEBIAN-CVE-2026-26080](https://patchblox.com/security/data/fix/linux/debian-cve-2026-26080.md) | Jul 21, 2026 |
| Linux | haproxy opensuse-leap 16.0 | 3.2.12+git0.6011f448e-160000.1.1 | [OPENSUSE-SU-2026:20290-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20290-1.md) | Feb 27, 2026 |
| Linux | haproxy sles 16.0 | 3.2.12+git0.6011f448e-160000.1.1 | [SUSE-SU-2026:20616-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20616-1.md) | Feb 27, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

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.