Patch tracker / CVE reference / CVE-2025-62567

CVE-2025-62567

CVE-2025-62567 is a Microsoft vulnerability that Microsoft rates Important, with a CVSS score of 5.3 (Medium). Microsoft has shipped the fix: deploy one of the 10 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Risk summary

Medium

5.3

CVSS v3

4.6%

EPSS, 30 days

Medium

Severity

Not in the CISA KEV catalog. EPSS exploit probability 4.6%. CVSS 5.3 (Medium).

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

Senserva AI Opinion for CVE-2025-62567

This is a denial of service flaw in Windows Hyper-V, rated High with a CVSS of 8.8, affecting Windows 10 Version 1809 x64 systems and Windows Server 2019. Anyone running Hyper-V hosts is exposed, since a successful attack can crash the hypervisor and take down every guest VM it hosts. EPSS puts exploitation probability at only 5 percent, so treat it as important but not an emergency.

Do this: Patch Hyper-V hosts running Windows 10 Version 1809 or Windows Server 2019 during the next maintenance window.

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

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

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-62567 (source: https://senserva.com/cve/CVE-2025-62567.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- CVE-2025-62567: Microsoft vulnerability, Microsoft rating Important, CVSS 5.3 (Medium)
- EPSS 30-day exploitation probability: 4.6%
- Actively exploited (CISA KEV): no
- Fixed by: KB5071413, KB5071417, KB5071503, KB5071542, KB5071543, KB5071544, KB5071546, KB5071547, KB5072014, KB5072033
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 as of 2026-10-19: not in the CISA KEV catalog, EPSS 5%.

Fixed by KB5071413 and 9 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.

Official patch(es) for CVE-2025-62567

Lower priority: patch in your normal cycle. In Intune or Defender, confirm whether the fixing updates KB5071413, KB5071417, KB5071503, KB5071542, KB5071543, KB5071544, KB5071546, KB5071547, KB5072014, KB5072033 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-62567. 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.

KB5071413 KB5071417 KB5071503 KB5071542 KB5071543 KB5071544 KB5071546 KB5071547 KB5072014 KB5072033

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-60710 CVE-2025-62221 CVE-2025-62456 CVE-2025-62549 CVE-2025-54100 CVE-2025-55233 CVE-2025-59516 CVE-2025-59517

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.