CVE-2026-68778

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

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: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

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

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

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
30(Track)
EG Risk 30/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
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
61%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 24, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

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

Vendor Advisories for CVE-2026-68778(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 30× in last 7d / 88× 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-09-24 22:53 UTCVendor advisory
  2. 2026-09-24 22:53 UTCGHSA enrichment
  3. 2026-09-24 20:39 UTCVendor advisory
  4. 2026-09-24 20:39 UTCGHSA enrichment
  5. 2026-09-24 17:24 UTCEG score recompute
  6. 2026-09-24 17:24 UTCVendor advisory
  7. 2026-09-24 17:24 UTCGHSA enrichment
  8. 2026-09-23 22:43 UTCVendor advisory
  9. 2026-09-23 22:43 UTCGHSA enrichment
  10. 2026-09-23 18:50 UTCEG score recompute
  11. 2026-09-23 18:50 UTCVendor advisory
  12. 2026-09-23 18:50 UTCGHSA enrichment
  13. 2026-09-23 17:54 UTCEPSS rescore
  14. 2026-09-22 18:06 UTCEG score recompute
  15. 2026-09-22 18:06 UTCVendor advisory
  16. 2026-09-22 18:06 UTCGHSA enrichment
  17. 2026-09-21 21:09 UTCEPSS rescore
  18. 2026-09-21 16:44 UTCVendor advisory
  19. 2026-09-21 16:44 UTCGHSA enrichment
  20. 2026-09-20 23:48 UTCEG score recompute
  21. 2026-09-20 23:48 UTCVendor advisory
  22. 2026-09-20 23:48 UTCGHSA enrichment
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-19 22:26 UTCEG score recompute
  25. 2026-09-19 22:26 UTCVendor advisory
Show 63 more
  1. 2026-09-19 22:26 UTCGHSA enrichment
  2. 2026-09-18 21:05 UTCEG score recompute
  3. 2026-09-18 21:05 UTCVendor advisory
  4. 2026-09-18 21:05 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 14:11 UTCVendor advisory
  7. 2026-09-18 14:11 UTCGHSA enrichment
  8. 2026-09-17 23:06 UTCVendor advisory
  9. 2026-09-17 23:06 UTCGHSA enrichment
  10. 2026-09-17 19:55 UTCEG score recompute
  11. 2026-09-17 19:55 UTCVendor advisory
  12. 2026-09-17 19:55 UTCGHSA enrichment
  13. 2026-09-16 22:11 UTCEG score recompute
  14. 2026-09-16 22:11 UTCVendor advisory
  15. 2026-09-16 22:11 UTCGHSA enrichment
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 22:47 UTCEG score recompute
  19. 2026-09-15 22:47 UTCVendor advisory
  20. 2026-09-15 22:47 UTCGHSA enrichment
  21. 2026-09-15 19:57 UTCEG score recompute
  22. 2026-09-15 19:57 UTCVendor advisory
  23. 2026-09-15 19:57 UTCGHSA enrichment
  24. 2026-09-15 17:57 UTCEG score recompute
  25. 2026-09-15 17:57 UTCVendor advisory
  26. 2026-09-15 17:57 UTCGHSA enrichment
  27. 2026-09-14 22:56 UTCVendor advisory
  28. 2026-09-14 22:56 UTCGHSA enrichment
  29. 2026-09-14 17:48 UTCVendor advisory
  30. 2026-09-14 17:48 UTCGHSA enrichment
  31. 2026-09-14 01:40 UTCEG score recompute
  32. 2026-09-14 01:40 UTCVendor advisory
  33. 2026-09-14 01:40 UTCGHSA enrichment
  34. 2026-09-13 00:19 UTCEG score recompute
  35. 2026-09-13 00:19 UTCVendor advisory
  36. 2026-09-13 00:19 UTCGHSA enrichment
  37. 2026-09-11 22:57 UTCVendor advisory
  38. 2026-09-11 22:57 UTCGHSA enrichment
  39. 2026-09-11 20:06 UTCVendor advisory
  40. 2026-09-11 20:06 UTCGHSA enrichment
  41. 2026-09-11 17:02 UTCEG score recompute
  42. 2026-09-11 17:02 UTCVendor advisory
  43. 2026-09-11 17:02 UTCGHSA enrichment
  44. 2026-09-11 14:53 UTCEPSS rescore
  45. 2026-09-11 09:37 UTCEPSS rescore
  46. 2026-09-10 23:36 UTCEG score recompute
  47. 2026-09-10 23:36 UTCGHSA enrichment
  48. 2026-09-09 22:13 UTCGHSA enrichment
  49. 2026-09-09 20:07 UTCVendor advisory
  50. 2026-09-09 20:07 UTCGHSA enrichment
  51. 2026-09-09 00:08 UTCEG score recompute
  52. 2026-09-09 00:08 UTCVendor advisory
  53. 2026-09-09 00:08 UTCGHSA enrichment
  54. 2026-09-08 21:49 UTCEG score recompute
  55. 2026-09-08 21:49 UTCVendor advisory
  56. 2026-09-08 21:49 UTCGHSA enrichment
  57. 2026-09-08 20:31 UTCEG score recompute
  58. 2026-09-08 20:31 UTCGHSA enrichment
  59. 2026-09-08 18:56 UTCEG score recompute
  60. 2026-09-08 18:56 UTCGHSA enrichment
  61. 2026-09-08 17:54 UTCEG score recompute
  62. 2026-09-08 17:54 UTCVendor advisory
  63. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-68778?
CVE-2026-68778 is a medium vulnerability 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-68778 disclosed?
CVE-2026-68778 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68778 actively exploited?
CVE-2026-68778 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 39.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68778?
CVE-2026-68778 has a CVSS v4.0 base score of 6.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-68778?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68778, 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-68778

Explore →

Is Your Infrastructure Affected by CVE-2026-68778?

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

Book a Demo →Browse All CVEs