Patch tracker / CVE reference / CVE-2025-62573

CVE-2025-62573

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

Risk summary

High

7.0

CVSS

4.6%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 4.6%. CVSS 7.0 (High).

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

Senserva AI Opinion for CVE-2025-62573

A DirectX Graphics Kernel bug here is rated High at 8.8 with a 5 percent EPSS score, notably lower exploit probability than the Critical, 73-percent DirectX Graphics Kernel CVEs elsewhere in this data set, though it affects the same Windows 10 version 1809 and Windows Server 2019 systems. It is a good reminder that not every bug in a heavily targeted component carries the same urgency. Not confirmed exploited or ransomware-linked.

Do this: Patch this alongside routine maintenance for Windows 10 1809 and Server 2019, after the higher-EPSS DirectX fixes are handled.

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

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

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-62573 (source: https://senserva.com/cve/CVE-2025-62573.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-62573: High severity Microsoft vulnerability, CVSS 7.0
- EPSS 30-day exploitation probability: 4.6%
- Actively exploited (CISA KEV): no
- Fixed by: KB5071413, KB5071417, 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: not in the CISA KEV catalog, EPSS 5%.

Fixed by KB5071413 and 8 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-62573

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5071413, KB5071417, 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-62573. 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 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.