OPENSUSE-SU-2026:20290-1: haproxy security update

OPENSUSE-SU-2026:20290-1, released February 27, 2026, fixes 2 CVEs in haproxy (version 3.2.12+git0.6011f448e-160000.1.1). None of them is reported as exploited. Patch Radar priority: Routine.

Routine

CVEs closed

None rated Critical

Exploited

None reported

Highest CVSS

4.8

Base score, 0 to 10

Highest EPSS

0.0055

46th percentile

Priority of the 2 CVEs

Patch now 0
                                Urgent 0
                                High 0
                                Routine 2

Fixed package versions

Product	Release	Fixed in
haproxy	opensuse-leap 16.0	3.2.12+git0.6011f448e-160000.1.1

CVEs this fix closes

Priority	CVE	Title	CVSS	EPSS	Exploitation
Routine	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.	3.7	0.0055	None reported
Routine	CVE-2026-26081	HAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format. HAProxy Enterprise and ALOHA are also affected.	4.8	0.0048	None reported

Also fixes CVE-2026-26080

SUSE-SU-2026:20616-1
haproxy on sles 16.0
DEBIAN-CVE-2026-26080
haproxy on Debian 14

Vendor advisory

https://osv.dev/vulnerability/openSUSE-SU-2026:20290-1

For tools and AI agents

This page as data: JSON · Markdown

Link to this page

If this page saved you time, a link to it in your ticket, advisory or write-up helps others find it.

HTML

<a href="https://patchblox.com/security/fix/linux/opensuse-su-2026-20290-1">OPENSUSE-SU-2026:20290-1 on Patchblox Patch Radar</a>

Reusing the data? How to credit Patch Radar.

Which servers are still behind?

Patchblox compares the installed package on every Linux machine against the fixed version for its release, including machines reported through Azure Update Manager.

Get a demo

Patch Radar data is free to use with attribution. Terms and how to credit it.

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.