CVE-2026-73028

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
8.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: 8.8Exploit: None knownExposed: 0

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

Improper access control in SQL Server allows an authorized attacker to elevate privileges over a network.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
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-73028

Vendor Advisories for CVE-2026-73028(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 49× in last 7d / 137× 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 137 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73028?
CVE-2026-73028 is a high vulnerability published on September 8, 2026. Improper access control in SQL Server allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-73028 disclosed?
CVE-2026-73028 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-73028 actively exploited?
CVE-2026-73028 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 46.1% of all scored CVEs.
What is the CVSS score of CVE-2026-73028?
CVE-2026-73028 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-73028?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73028, 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-73028

Explore →

Is Your Infrastructure Affected by CVE-2026-73028?

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

Book a Demo →Browse All CVEs