CVE-2026-45583

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.7% (52nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.5 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 2026-06-09) is not newer than that change (2026-09-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
8.1EG
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: 0.7%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper control of generation of code ('code injection') in Microsoft Exchange Server allows an unauthorized attacker to execute code over a network.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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 (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.7% × 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
0.7%
EPSS %ILE
52nd
KEV
Not listed

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.

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

June 9, 2026

Last Modified

September 24, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45583

Vendor Advisories for CVE-2026-45583(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 11× in last 7d / 29× 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 100 of 383 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. None are among the latest 100 rows. The 283 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45583?
CVE-2026-45583 is a high-severity vulnerability; its CVE record was published on June 9, 2026. Improper control of generation of code ('code injection') in Microsoft Exchange Server allows an unauthorized attacker to execute code over a network.
When was CVE-2026-45583 made public?
CVE-2026-45583 was made public on June 9, 2026: 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 June 9, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-45583 actively exploited?
CVE-2026-45583 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45583?
CVE-2026-45583 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-45583?
A fix for CVE-2026-45583 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45583 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45583

Explore →

Is Your Infrastructure Affected by CVE-2026-45583?

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

Book a Demo →Browse All CVEs