CVE-2026-26081HAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format.
Updated under an hour ago ()
Does this affect you?
It affects haproxy and 2 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 4.8 MEDIUM (v3.1, NVD)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
- Weakness (CWE)
- CWE-130
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Aug 25, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
haproxy haproxy haproxy:haproxy | from 3.0.0 before 3.0.16; from 3.1 before 3.1.14; from 3.2 before 3.2.12; from 3.3 before 3.3.3 | NVD |
haproxy aloha haproxy:aloha | from 16.5.0.0 before 16.5.30; from 17.0.0 before 17.0.18; from 17.5.0 before 17.5.16 | NVD |
haproxy haproxy_enterprise haproxy:haproxy_enterprise | 3.0r1; 3.0r1; 3.0r1; 3.0r1; 3.0r1; 3.0r1; 3.0r1; 3.0r1; and 73 more ranges | NVD |
References
- https://git.haproxy.org/?p=haproxy-3.2.git;a=commit;h=4765277f4f915baac2d57db63538ff0a59966debpatch, vendor-advisory
- https://www.haproxy.orgproduct
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.