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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 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
48.4%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 25, 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 12× in last 7d / 47× 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-07-25 14:18 UTCEPSS rescore
  2. 2026-07-24 14:17 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 03:12 UTCEG score recompute
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 03:42 UTCEG score recompute
  10. 2026-07-19 03:42 UTCVendor advisory
  11. 2026-07-19 03:42 UTCGHSA enrichment
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-17 05:36 UTCVendor advisory
  15. 2026-07-17 05:36 UTCGHSA enrichment
  16. 2026-07-17 01:35 UTCVendor advisory
  17. 2026-07-17 01:35 UTCGHSA enrichment
  18. 2026-07-16 21:33 UTCVendor advisory
  19. 2026-07-16 21:33 UTCGHSA enrichment
  20. 2026-07-16 17:32 UTCVendor advisory
  21. 2026-07-16 17:32 UTCGHSA enrichment
  22. 2026-07-16 17:03 UTCEPSS rescore
  23. 2026-07-16 13:31 UTCVendor advisory
  24. 2026-07-16 13:31 UTCGHSA enrichment
  25. 2026-07-16 09:30 UTCGHSA enrichment
Show 22 more
  1. 2026-07-16 05:30 UTCVendor advisory
  2. 2026-07-16 05:30 UTCGHSA enrichment
  3. 2026-07-16 01:29 UTCVendor advisory
  4. 2026-07-16 01:29 UTCGHSA enrichment
  5. 2026-07-15 21:28 UTCVendor advisory
  6. 2026-07-15 21:28 UTCGHSA enrichment
  7. 2026-07-15 17:27 UTCVendor advisory
  8. 2026-07-15 17:27 UTCGHSA enrichment
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 13:25 UTCVendor advisory
  11. 2026-07-15 13:25 UTCGHSA enrichment
  12. 2026-07-15 09:20 UTCVendor advisory
  13. 2026-07-15 09:20 UTCGHSA enrichment
  14. 2026-07-15 05:18 UTCVendor advisory
  15. 2026-07-15 05:18 UTCGHSA enrichment
  16. 2026-07-15 01:17 UTCVendor advisory
  17. 2026-07-15 01:17 UTCGHSA enrichment
  18. 2026-07-14 21:16 UTCVendor advisory
  19. 2026-07-14 21:16 UTCGHSA enrichment
  20. 2026-07-14 17:15 UTCEG score recompute
  21. 2026-07-14 17:15 UTCVendor advisory
  22. 2026-07-14 17:10 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

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 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-42990 actively exploited?
CVE-2026-42990 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 48.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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