CVE-2026-45583 json
Microsoft Exchange Server Remote Code Execution Vulnerability
published 5mo ago modified last mo. also EUVD-2026-35681
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
Improper control of generation of code ('code injection') in Microsoft Exchange Server allows an unauthorized attacker to execute code over a network.
Patch / fix
- Microsoft Microsoft Exchange Server 2016 Cumulative Update 23 15.01.2507.071
- Microsoft Microsoft Exchange Server 2019 Cumulative Update 14 15.02.1544.043
- Microsoft Microsoft Exchange Server 2019 Cumulative Update 15 15.02.1748.048
- Microsoft Microsoft Exchange Server Subscription Edition RTM 15.02.2562.045
Is CVE-2026-45583 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 4mo ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Microsoft Exchange Server 2016 Cumulative Update 23
- Microsoft Microsoft Exchange Server 2019 Cumulative Update 14
- Microsoft Microsoft Exchange Server 2019 Cumulative Update 15
- Microsoft Microsoft Exchange Server Subscription Edition RTM
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
- Technology feeds
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-45583
vendor-advisory, patch
Sources
- CVE List CVE-2026-45583
- NVD CVE-2026-45583
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.