CVE-2026-85088

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-91418 (ENISA EUVD) · GHSA-4xmj-xwhr-jcj2 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Validation of Certificate with Host Mismatch in the C++ and D libraries of Apache Thrift.

Both libraries install a default access manager for client sockets — TSSLSocketFactory does so in C++, and the accessManager property does so in D — which compares the peer certificate against the host

name that was connected to. That comparison walks the subjectAltName dNSName entries first and consults the certificate Common Name afterwards. A name that does not match yields a "skip" result rather than

a rejection, so a certificate whose subjectAltName entries are all present and all non-matching falls through to the Common Name, which can then satisfy the check.

RFC 6125 section 6.4.4, and RFC 9525 section 2, require that the Common Name is not consulted when a dNSName subjectAltName is present. A certificate carrying subjectAltName entries for one name and a

Common Name for another is therefore accepted for a connection to the second name.

Exploitation requires an attacker positioned on the network path who holds a certificate that chains to a certificate authority in the client's trust store and whose Common Name matches the connected host

name. Public certificate authorities have not issued on Common Name alone for many years, so this is principally a concern for deployments using a private or enterprise public-key infrastructure.

This issue affects the C++ library of Apache Thrift from 0.7.0 through 0.24.0 and the D library from 0.9.0 through 0.24.0. Users should upgrade to 0.25.0.

CVSS
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 2, 2026

Last Modified

October 2, 2026

Advisory Details (2)

Auto-updated Oct 2, 2026
Patch available.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatthrift-main-0.25.0-0.1.hum12026-10-01redhat

These rows come from Red Hat. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
thrift0.17.0-2 ... 0.24.0-2 (21 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
thrift0.19.0-4 ... 0.24.0-2 (11 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
thrift0.19.0-4 ... 0.24.0-2 (11 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 103 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 3 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-85088?
CVE-2026-85088 is a medium-severity vulnerability; its CVE record was published on October 2, 2026. Improper Validation of Certificate with Host Mismatch in the C++ and D libraries of Apache Thrift. Both libraries install a default access manager for client sockets — TSSLSocketFactory does so in C++, and the accessManager property does so in D — which compares the peer certificate against the…
When was the CVE record for CVE-2026-85088 published?
The CVE record for CVE-2026-85088 was published on October 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 2, 2026; the record at its source may have been updated since.
Is CVE-2026-85088 actively exploited?
CVE-2026-85088 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85088?
CVE-2026-85088 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85088?
A fix for CVE-2026-85088 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-85088 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85088?

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