CVE-2023-21769

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 89% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2023-25936 (ENISA EUVD) · GHSA-9pvf-crwc-vr62 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
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 exploitation likelihood — EPSS 89%
CISA-KEV: Not listedEPSS PROB: 89%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Microsoft Message Queuing (MSMQ) Denial of Service Vulnerability

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
84
EG Risk 84/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation89% × 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 partial (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
89%
EPSS %ILE
99th
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
89% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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: 14 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 partial (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; 60 days if it is not.

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

April 11, 2023

Last Modified

January 1, 2025

Advisory Details (1)

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

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-21769

Vendor Advisories for CVE-2023-21769(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 13× in last 7d / 55× 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 175 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 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-21769?
CVE-2023-21769 is a critical-severity vulnerability; its CVE record was published on April 11, 2023. Microsoft Message Queuing (MSMQ) Denial of Service Vulnerability
When was CVE-2023-21769 made public?
CVE-2023-21769 was made public on April 11, 2023: 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 April 11, 2023. EchelonGraph's copy of the record carries a last-modified date of January 1, 2025; the record at its source may have been updated since.
Is CVE-2023-21769 actively exploited?
CVE-2023-21769 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 89% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-21769?
CVE-2023-21769 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-21769?
A fix for CVE-2023-21769 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-21769 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-21769

Explore →

Is Your Infrastructure Affected by CVE-2023-21769?

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