Patch tracker / CVE reference / CVE-2025-54906

CVE-2025-54906

CVE-2025-54906 is a high severity Microsoft vulnerability with a CVSS score of 7.8. Its EPSS score puts the probability of exploitation in the next 30 days at 19%. Microsoft has shipped the fix: deploy one of the 5 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

7.8

CVSS

19%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 19%. CVSS 7.8 (High).

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

Senserva AI Opinion for CVE-2025-54906

This Office remote code execution flaw stands out from the batch because SharePoint Enterprise Server 2016 and SharePoint Server 2019 are on the affected list, and its 18 percent EPSS score is well above the neighboring Office bugs. A crafted document processed by SharePoint's server-side Office components can compromise the farm itself, not just one workstation. Severity is High at CVSS 8.8, and on-premises SharePoint remains a favorite target for attackers.

Do this: Patch on-premises SharePoint 2016 and 2019 servers ahead of desktop Office clients this cycle.

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

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

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-54906 (source: https://senserva.com/cve/CVE-2025-54906.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-54906: High severity Microsoft vulnerability, CVSS 7.8
- EPSS 30-day exploitation probability: 19%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002576, KB5002766, KB5002775, KB5002778, KB5002781
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.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 19%).

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

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2025-54906

Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. In Intune or Defender, confirm whether the fixing updates KB5002576, KB5002766, KB5002775, KB5002778, KB5002781 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-54906. 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.

KB5002576 KB5002766 KB5002775 KB5002778 KB5002781

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-54897 CVE-2025-54910 CVE-2025-54905

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.