CVE-2023-28302

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 93% 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
Trending — 4 sources updated this weekElevated
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 93%
CISA-KEV: Not listedEPSS PROB: 93%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
86
EG Risk 86/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.
Exploitation93% × 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
93%
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
93% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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: 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.

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 14, 2026
Patch available. Sources: microsoft.
Microsoft

Security Update Guide - Microsoft Security Response Center

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

Vendor Advisories for CVE-2023-28302(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 23× in last 7d / 40× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 81 of 94 refreshes 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. 19 repeat rows among the latest 100 are merged into the row they repeat. The 13 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 10:28 UTCEG score recompute
  2. 2026-10-23 10:28 UTCVendor advisory
  3. 2026-10-23 10:27 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-10-22 16:31 UTCEPSS rescoreEPSS 93% · 99th percentile
  5. 2026-10-22 12:42 UTCEG score recompute
  6. 2026-10-22 12:42 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-10-21 14:57 UTCEG score recompute
  8. 2026-10-21 14:57 UTCVendor advisory
  9. 2026-10-21 14:56 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-10-20 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  11. 2026-10-20 16:22 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-10-19 17:46 UTCEG score recompute
  13. 2026-10-19 17:46 UTCVendor advisory
  14. 2026-10-19 17:46 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-10-18 19:59 UTCEG score recompute
  16. 2026-10-18 19:59 UTCVendor advisory
  17. 2026-10-18 19:59 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-10-18 08:07 UTCEG score recompute
  19. 2026-10-17 22:12 UTCEG score recompute
  20. 2026-10-17 22:12 UTCVendor advisory
  21. 2026-10-17 22:12 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  22. 2026-10-17 00:26 UTCEG score recompute
  23. 2026-10-17 00:26 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-10-15 23:57 UTCEG score recompute
  25. 2026-10-15 23:57 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
Show 56 more
  1. 2026-10-14 16:29 UTCEPSS rescoreEPSS 93% · 99th percentile
  2. 2026-10-14 15:56 UTCEG score recompute
  3. 2026-10-14 15:55 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-10-13 15:05 UTCVendor advisory
  5. 2026-10-13 15:04 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-12 17:18 UTCEG score recompute
  7. 2026-10-12 17:18 UTCVendor advisory
  8. 2026-10-12 17:18 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  9. 2026-10-11 21:55 UTCEG score recompute
  10. 2026-10-08 17:06 UTCEPSS rescoreEPSS 93% · 99th percentile
  11. 2026-10-03 14:23 UTCEPSS rescoreEPSS 93% · 99th percentile
  12. 2026-10-01 19:47 UTCEPSS rescoreEPSS 93% · 99th percentile
  13. 2026-09-30 16:20 UTCEG score recompute
  14. 2026-09-30 15:01 UTCEPSS rescoreEPSS 93% · 99th percentile
  15. 2026-09-24 14:01 UTCEPSS rescoreEPSS 93% · 99th percentile
  16. 2026-09-23 13:45 UTCEPSS rescoreEPSS 93% · 99th percentile
  17. 2026-09-22 14:45 UTCEPSS rescoreEPSS 93% · 99th percentile
  18. 2026-09-12 14:58 UTCEPSS rescoreEPSS 93% · 99th percentile
  19. 2026-09-06 13:45 UTCEPSS rescoreEPSS 93% · 99th percentile
  20. 2026-09-05 15:25 UTCEPSS rescoreEPSS 93% · 99th percentile
  21. 2026-09-02 14:09 UTCEPSS rescoreEPSS 93% · 99th percentile
  22. 2026-08-30 19:15 UTCEPSS rescoreEPSS 93% · 99th percentile
  23. 2026-08-28 21:38 UTCEPSS rescoreEPSS 93% · 99th percentile
  24. 2026-08-26 14:43 UTCEPSS rescoreEPSS 93% · 99th percentile
  25. 2026-08-24 14:14 UTCEPSS rescoreEPSS 93% · 99th percentile
  26. 2026-08-21 23:46 UTCEPSS rescoreEPSS 93% · 99th percentile
  27. 2026-08-18 13:46 UTCEPSS rescoreEPSS 93% · 99th percentile
  28. 2026-08-15 01:28 UTCEPSS rescoreEPSS 94% · 99th percentile
  29. 2026-08-05 19:15 UTCEPSS rescoreEPSS 94% · 99th percentile
  30. 2026-07-30 01:28 UTCEPSS rescoreEPSS 94% · 99th percentile
  31. 2026-07-23 02:20 UTCEG score recompute
  32. 2026-07-22 21:23 UTCEG score recompute▲ 1.50
  33. 2026-07-22 21:23 UTCVendor advisory
  34. 2026-07-22 21:23 UTCGHSA enrichmentGHSA-j2x9-pqv3-56mg · GitHub severity HIGH · GitHub CVSS 7.5
  35. 2026-07-22 14:06 UTCEPSS rescoreEPSS 94% · 99th percentile
  36. 2026-07-21 15:23 UTCEPSS rescoreEPSS 94% · 99th percentile
  37. 2026-07-19 14:29 UTCEPSS rescoreEPSS 94% · 99th percentile
  38. 2026-07-13 22:28 UTCEPSS rescoreEPSS 94% · 99th percentile
  39. 2026-07-12 05:45 UTCEPSS rescoreEPSS 94% · 99th percentile
  40. 2026-07-11 08:25 UTCEPSS rescoreEPSS 94% · 99th percentile
  41. 2026-06-22 14:24 UTCEPSS rescoreEPSS 94% · 99th percentile
  42. 2026-06-16 17:51 UTCEPSS rescoreEPSS 94% · 99th percentile
  43. 2026-06-15 17:47 UTCEPSS rescoreEPSS 94% · 99th percentile
  44. 2026-06-13 22:59 UTCEPSS rescoreEPSS 35% · 97th percentile
  45. 2026-06-12 23:10 UTCEPSS rescoreEPSS 35% · 97th percentile
  46. 2026-06-11 13:59 UTCEPSS rescoreEPSS 35% · 97th percentile
  47. 2026-06-10 22:17 UTCEPSS rescoreEPSS 35% · 97th percentile
  48. 2026-06-10 13:21 UTCEPSS rescoreEPSS 35% · 97th percentile
  49. 2026-06-07 15:23 UTCEPSS rescoreEPSS 35% · 97th percentile
  50. 2026-06-06 13:46 UTCEPSS rescoreEPSS 35% · 97th percentile
  51. 2026-06-05 22:46 UTCEPSS rescoreEPSS 35% · 97th percentile
  52. 2026-06-05 06:09 UTCEPSS rescoreEPSS 35% · 97th percentile
  53. 2026-06-02 20:12 UTCEPSS rescoreEPSS 35% · 97th percentile
  54. 2026-06-01 13:51 UTCEPSS rescoreEPSS 35% · 97th percentile
  55. 2026-05-31 22:29 UTCEPSS rescoreEPSS 35% · 97th percentile
  56. 2026-05-31 00:15 UTCEPSS rescoreEPSS 35% · 97th percentile

Frequently asked(5)

What is CVE-2023-28302?
CVE-2023-28302 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-28302 made public?
CVE-2023-28302 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-28302 actively exploited?
CVE-2023-28302 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-28302?
CVE-2023-28302 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-28302?
A fix for CVE-2023-28302 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-28302 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-28302?

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