CVE-2021-24112

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

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

Also known asEUVD-2022-5253 (ENISA EUVD) · GHSA-rxg9-xrhp-64gj (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

.NET Core Remote Code Execution Vulnerability

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
61
EG Risk 61/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.
Exploitation3.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
3.7%
EPSS %ILE
90th
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.GitHub Security Advisory CVSS
EG Likelihood
3.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

February 25, 2021

Last Modified

October 7, 2026

Advisory Details (1)

Auto-updated Nov 15, 2026
Patch available. Sources: microsoft.
Microsoft

Security Update Guide - Microsoft Security Response Center

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-24112

Vendor and National Authority Advisories for CVE-2021-24112(3)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
nugetSystem.Drawing.Common @ 4.7.2 (fixes >= 4.0.0, < 4.7.2)—ghsa
nugetSystem.Drawing.Common @ 5.0.3 (fixes >= 5.0.0, < 5.0.3)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
System.Drawing.Common5.0.0, 5.0.1, 5.0.2
  • 4.0.0 up to 4.7.2: fixed in 4.7.2
  • 5.0.0 up to 5.0.3: fixed in 5.0.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 74× 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 326 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 226 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2021-24112?
CVE-2021-24112 is a critical-severity vulnerability; its CVE record was published on February 25, 2021. .NET Core Remote Code Execution Vulnerability
When was CVE-2021-24112 made public?
CVE-2021-24112 was made public on February 9, 2021: 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 February 25, 2021. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2021-24112 actively exploited?
CVE-2021-24112 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.7% probability of exploitation in the next 30 days (90th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-24112?
CVE-2021-24112 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2021-24112?
A fix for CVE-2021-24112 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-24112 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2021-24112 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-24112

Explore →

Is Your Infrastructure Affected by CVE-2021-24112?

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