CVE-2026-26081

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

Score 4.8 from GitHub Security Advisory published 2026-07-20. a secondary CVSS source baseline 4.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
4.8
EG Score
4.8(medium)
EG Risk
22(Track)
EG Risk 22/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 20, 2026

Last Modified

August 25, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
No patch confirmed yet.
generic

HAProxy - The Reliable, High Perf. TCP/HTTP Load Balancer

https://www.haproxy.org
generic

Repositories - haproxy-3.2.git/commit

https://git.haproxy.org/?p=haproxy-3.2.git;a=commit;h=4765277f4f915baac2d57db63538ff0a59966deb

Vendor Advisories for CVE-2026-26081(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuvim-haproxy (3.0.12-0ubuntu0.25.10.3) @ questing2026-09-11ubuntu
redhathaproxy-main-3.0.25-0.1.1.hum12026-07-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
haproxy3.0.11-1, 3.0.11-1+deb13u13.0.11-1+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
haproxy3.0.11-1 ... 3.2.9-1 (22 versions)3.2.11-2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 90× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 169 total refreshes for this CVE.

  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:38 UTCEG score recompute
  3. 2026-09-11 09:38 UTCVendor advisory
  4. 2026-09-11 09:38 UTCGHSA enrichment
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-09 12:21 UTCEG score recompute
  7. 2026-09-09 12:21 UTCVendor advisory
  8. 2026-09-09 12:21 UTCGHSA enrichment
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 23:03 UTCEG score recompute
  11. 2026-09-07 23:03 UTCVendor advisory
  12. 2026-09-07 23:03 UTCGHSA enrichment
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-06 11:58 UTCEG score recompute
  17. 2026-09-06 11:58 UTCVendor advisory
  18. 2026-09-06 11:58 UTCGHSA enrichment
  19. 2026-09-05 09:43 UTCEG score recompute
  20. 2026-09-05 09:43 UTCVendor advisory
  21. 2026-09-05 09:43 UTCGHSA enrichment
  22. 2026-09-04 05:06 UTCEPSS rescore
  23. 2026-09-02 14:11 UTCEPSS rescore
  24. 2026-09-01 13:53 UTCEPSS rescore
  25. 2026-09-01 04:39 UTCEPSS rescore
Show 75 more
  1. 2026-08-31 02:47 UTCEG score recompute
  2. 2026-08-31 02:47 UTCVendor advisory
  3. 2026-08-31 02:47 UTCGHSA enrichment
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 02:42 UTCEG score recompute
  6. 2026-08-30 02:42 UTCVendor advisory
  7. 2026-08-30 02:42 UTCGHSA enrichment
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 22:16 UTCEG score recompute
  11. 2026-08-27 22:16 UTCVendor advisory
  12. 2026-08-27 22:16 UTCGHSA enrichment
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 22:12 UTCEG score recompute
  15. 2026-08-26 22:12 UTCVendor advisory
  16. 2026-08-26 22:12 UTCGHSA enrichment
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 15:51 UTCEG score recompute
  19. 2026-08-25 15:51 UTCVendor advisory
  20. 2026-08-25 15:51 UTCGHSA enrichment
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-24 23:17 UTCEG score recompute
  23. 2026-08-24 23:17 UTCVendor advisory
  24. 2026-08-24 23:17 UTCGHSA enrichment
  25. 2026-08-23 23:13 UTCEG score recompute
  26. 2026-08-23 23:13 UTCVendor advisory
  27. 2026-08-23 23:13 UTCGHSA enrichment
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-22 23:10 UTCEG score recompute
  30. 2026-08-22 23:10 UTCVendor advisory
  31. 2026-08-22 23:10 UTCGHSA enrichment
  32. 2026-08-21 23:49 UTCEPSS rescore
  33. 2026-08-21 23:06 UTCVendor advisory
  34. 2026-08-21 23:06 UTCGHSA enrichment
  35. 2026-08-20 22:59 UTCEG score recompute
  36. 2026-08-20 22:59 UTCVendor advisory
  37. 2026-08-20 22:59 UTCGHSA enrichment
  38. 2026-08-20 22:55 UTCEPSS rescore
  39. 2026-08-19 22:55 UTCEG score recompute
  40. 2026-08-19 22:55 UTCVendor advisory
  41. 2026-08-19 22:55 UTCGHSA enrichment
  42. 2026-08-19 17:03 UTCEPSS rescore
  43. 2026-08-18 19:38 UTCEG score recompute
  44. 2026-08-18 19:38 UTCVendor advisory
  45. 2026-08-18 19:38 UTCGHSA enrichment
  46. 2026-08-18 13:48 UTCEPSS rescore
  47. 2026-08-17 15:53 UTCEG score recompute
  48. 2026-08-17 15:53 UTCVendor advisory
  49. 2026-08-17 15:53 UTCGHSA enrichment
  50. 2026-08-17 13:47 UTCEPSS rescore
  51. 2026-08-16 15:49 UTCEG score recompute
  52. 2026-08-16 15:49 UTCVendor advisory
  53. 2026-08-16 15:49 UTCGHSA enrichment
  54. 2026-08-16 14:56 UTCEPSS rescore
  55. 2026-08-16 02:14 UTCEPSS rescore
  56. 2026-08-15 15:46 UTCEG score recompute
  57. 2026-08-15 15:46 UTCVendor advisory
  58. 2026-08-15 15:46 UTCGHSA enrichment
  59. 2026-08-15 01:30 UTCEPSS rescore
  60. 2026-08-14 15:42 UTCEG score recompute
  61. 2026-08-14 15:42 UTCVendor advisory
  62. 2026-08-14 15:42 UTCGHSA enrichment
  63. 2026-08-13 22:00 UTCEPSS rescore
  64. 2026-08-13 15:38 UTCVendor advisory
  65. 2026-08-13 15:38 UTCGHSA enrichment
  66. 2026-08-12 15:34 UTCEG score recompute
  67. 2026-08-12 15:34 UTCVendor advisory
  68. 2026-08-12 15:34 UTCGHSA enrichment
  69. 2026-08-12 13:50 UTCEPSS rescore
  70. 2026-08-11 15:15 UTCEG score recompute
  71. 2026-08-11 15:14 UTCVendor advisory
  72. 2026-08-11 15:14 UTCGHSA enrichment
  73. 2026-08-11 13:42 UTCEPSS rescore
  74. 2026-08-11 00:00 UTCEPSS rescore
  75. 2026-08-10 15:11 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-26081?
CVE-2026-26081 is a medium vulnerability published on July 20, 2026. 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.
When was CVE-2026-26081 disclosed?
CVE-2026-26081 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26081 actively exploited?
CVE-2026-26081 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.3% of all scored CVEs.
What is the CVSS score of CVE-2026-26081?
CVE-2026-26081 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-26081?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26081, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26081

Explore →

Is Your Infrastructure Affected by CVE-2026-26081?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs