CVE-2026-45389

CRITICALPre-NVD 7.49.1
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.4; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2026-36765 (ENISA EUVD) · GHSA-8wf9-g5q8-gg97 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's description, written by its CNA (MITRE Corporation), states the affected versions: "In OCaml-TLS before 2.1.0, the server implementation does insufficient checks of the certificate provided by the client (when doing client authentication), which allows impersonation with certificates that are not meant…" No release containing a fix is confirmed on record.

In OCaml-TLS before 2.1.0, the server implementation does insufficient checks of the certificate provided by the client (when doing client authentication), which allows impersonation with certificates that are not meant for client authentication (because of KeyUsage and ExtendedKeyUsage).

CVSS v3
7.4
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
8th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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: 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).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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.

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

June 15, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jun 16, 2026
No fix on record yet.
Web page

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/OSEC-2026-07

Vendor Advisories for CVE-2026-45389(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 73× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 459 refreshes 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 359 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-45389?
CVE-2026-45389 is a critical-severity vulnerability; its CVE record was published on June 15, 2026. In OCaml-TLS before 2.1.0, the server implementation does insufficient checks of the certificate provided by the client (when doing client authentication), which allows impersonation with certificates that are not meant for client authentication (because of KeyUsage and ExtendedKeyUsage).
When was the CVE record for CVE-2026-45389 published?
The CVE record for CVE-2026-45389 was published on June 15, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-45389 actively exploited?
CVE-2026-45389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45389?
CVE-2026-45389 has a CVSS v3.1 base score of 7.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises CISA-ADP (Vulnrichment) CVSS v3.1 + FIRST EPSS + GHSA into a combined EG score of 9.1 (CRITICAL).
How do I remediate CVE-2026-45389?
No fix for CVE-2026-45389 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (MITRE Corporation), states the affected versions: "In OCaml-TLS before 2.1.0, the server implementation does insufficient checks of the certificate provided by the client (when doing client authentication), which allows impersonation with certificates that are not meant…" No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-45389 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45389

Explore →

Is Your Infrastructure Affected by CVE-2026-45389?

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