Patch tracker / CVE reference / CVE-2025-59261

CVE-2025-59261

CVE-2025-59261 is a high severity Microsoft vulnerability with a CVSS score of 7.0. 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.

Risk summary

High

7.0

CVSS v3

6.0%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 6.0%. 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-59261

A third Windows Graphics Component bug in this data, Critical at 9.9 with a 6 percent EPSS score, affects Windows Server 2022, its Server Core edition, and the older Windows 11 22H2 on ARM64. Finding graphics-component vulnerabilities on server builds is a reminder that Server Core still ships enough graphics stack to be affected even without a full desktop experience. Not confirmed exploited or ransomware-linked.

Do this: Patch Server 2022, including Server Core installs, for this Graphics Component fix alongside the client-side variants.

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

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

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-59261 (source: https://senserva.com/cve/CVE-2025-59261.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-59261: High severity Microsoft vulnerability, CVSS 7.0
- EPSS 30-day exploitation probability: 6.0%
- Actively exploited (CISA KEV): no
- Fixed by: KB5066780, KB5066782, KB5066793, KB5066835
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 6%.

Fixed by KB5066780 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.

Official patch(es) for CVE-2025-59261

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5066780, KB5066782, KB5066793, KB5066835 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-59261. 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.

KB5066780 KB5066782 KB5066793 KB5066835

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-24990 CVE-2025-59230 CVE-2025-47827 CVE-2016-9535 CVE-2025-49708 CVE-2025-58719 CVE-2025-59280 CVE-2025-59284

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.