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 mishand
29
Routine
LOW 3.7REMOTEUPGRADEUPGRADEDOWNGRADE
CVE-2026-26080 is a low-severity flaw (CVSS 3.7) affecting haproxy, aloha, haproxy enterprise. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official sourceNVD · CVE Program · Report a problem with this page Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-26080?
haproxy: upgrade to 3.2.12, 3.3.3; aloha: upgrade to 17.0.18, 17.5.16; haproxy enterprise: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2026-26080 being exploited?
CVE-2026-26080 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-26080 affect?
CVE-2026-26080 affects haproxy, aloha, haproxy enterprise. Severity is low (CVSS 3.7). 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.
How urgent is CVE-2026-26080?
Priority 29/100. Remotely exploitable, no login, no user action