CVE-2026-42990

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-14. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

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

Heap-based buffer overflow in SQL Server ODBC driver allows an unauthorized attacker to execute code over a network.

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

Published

July 14, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated Jul 28, 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-42990

Vendor Advisories for CVE-2026-42990(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 61× in last 7d / 104× 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.

Showing the most recent 100 of 104 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42990?
CVE-2026-42990 is a critical vulnerability published on July 14, 2026. Heap-based buffer overflow in SQL Server ODBC driver allows an unauthorized attacker to execute code over a network.
When was CVE-2026-42990 disclosed?
CVE-2026-42990 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42990 actively exploited?
CVE-2026-42990 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 51.6% of all scored CVEs.
What is the CVSS score of CVE-2026-42990?
CVE-2026-42990 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-42990?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42990, 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-42990

Explore →

Is Your Infrastructure Affected by CVE-2026-42990?

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

Start Free Scan →Browse All CVEs