CVE-2026-26081

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 4 sources updated this week
4.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.8Exploit: NoneExposed: 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(low)
EPSS
28.8%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 21, 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(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuvim-haproxy (3.0.12-0ubuntu0.25.10.3) @ questing2026-07-20ubuntu

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.

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 16:56 UTCEG score recompute
  6. 2026-07-20 16:56 UTCVendor advisory
  7. 2026-07-20 16:04 UTCEG score recompute
  8. 2026-07-20 16:04 UTCVendor advisory
  9. 2026-07-20 16:02 UTCMITRE cvelistV5first tracked

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 July 21, 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 28.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-26081?
CVE-2026-26081 has a CVSS v3 base score of 4.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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

Explore the affected products and dependency analysis for 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