CVE-2024-37341

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.4% (73rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-09-10) is not newer than that change (2026-08-10), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-36963 (ENISA EUVD) · GHSA-c5m2-6p7h-vxqm (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Microsoft SQL Server Elevation of Privilege Vulnerability

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.4% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.4%
EPSS %ILE
73rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 10, 2024

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Oct 31, 2026
Patch available. Sources: microsoft.
Microsoft

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-37341

Vendor Advisories for CVE-2024-37341(1)

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 17× in last 7d / 77× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 306 rows 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 206 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-37341?
CVE-2024-37341 is a critical-severity vulnerability; its CVE record was published on September 10, 2024. Microsoft SQL Server Elevation of Privilege Vulnerability
When was CVE-2024-37341 made public?
CVE-2024-37341 was made public on September 10, 2024: 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 10, 2024. EchelonGraph's copy of the record carries a last-modified date of August 10, 2026; the record at its source may have been updated since.
Is CVE-2024-37341 actively exploited?
CVE-2024-37341 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-37341?
CVE-2024-37341 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-37341?
A fix for CVE-2024-37341 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-37341 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-37341

Explore →

Is Your Infrastructure Affected by CVE-2024-37341?

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