CVE-2026-67389

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory published 2026-09-08. The CNA's CVSS baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
6.5EG
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: 1.0%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Out-of-bounds read in SQL Server allows an authorized attacker to disclose information over a network.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
30
EG Risk 30/100

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 (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation1.0% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
1.0%
EPSS %ILE
61st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

September 8, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67389

Vendor Advisories for CVE-2026-67389(2)

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 21× in last 7d / 122× 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 155 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 55 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67389?
CVE-2026-67389 is a medium-severity vulnerability; its CVE record was published on September 8, 2026. Out-of-bounds read in SQL Server allows an authorized attacker to disclose information over a network.
When was CVE-2026-67389 made public?
CVE-2026-67389 was made public on September 8, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on September 8, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-67389 actively exploited?
CVE-2026-67389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67389?
CVE-2026-67389 has a CVSS base score of 6.5 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-67389?
A fix for CVE-2026-67389 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67389 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-67389?

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

Book a Demo →Browse All CVEs