Patch tracker / CVE reference / CVE-2025-59249

CVE-2025-59249

CVE-2025-59249 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Microsoft has shipped the fix: deploy one of the 4 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

High

High severity Microsoft vulnerability, CVSS 8.8. Fixed by 4 Microsoft security updates.

Senserva AI read on CVE-2025-59249 Official patches for CVE-2025-59249 Change history Admin questions

Risk summary

CVSS base

8.8

EPSS exploit probability

<1%

Severity

High

Senserva AI Opinion for CVE-2025-59249

Exchange Server privilege escalation flaws are prized by attackers because Exchange holds mail for the whole organization and often runs with high directory privileges. This one is rated High Severity at CVSS 8.8 and affects Exchange 2016 CU23 and Exchange 2019 CU14 and CU15, with a low 1% EPSS score at present.

Do this: Update on-premises Exchange 2016 and 2019 servers now, and treat any Exchange box that cannot be patched as a candidate for migration.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2025-59249

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2025-59249 (source: https://senserva.com/cve/CVE-2025-59249.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-59249: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: <1%
- Actively exploited (CISA KEV): no
- Fixed by: KB5066366, KB5066367, KB5066368, KB5066369
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS under 1%.

Fixed by KB5066366 and 3 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Updated August 7, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2025-59249

Published

2025-10-14

Last revised

2025-10-14

Changes tracked

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Exploitation and severity

Not in the CISA KEV catalog. EPSS exploit probability <1%. CVSS 8.8 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Official patch(es) for CVE-2025-59249

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5066366, KB5066367, KB5066368, KB5066369 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2025-59249. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5066366 KB5066367 KB5066368 KB5066369

Affected products

Fixed by the same updates

If you are patching CVE-2025-59249, the same updates also fix these:

CVE-2025-53782 CVE-2025-59248

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.