Patch tracker / CVE reference / CVE-2025-62555

CVE-2025-62555

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

CVSS v3

<1%

EPSS, 30 days

High

Severity

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

This is a Remote Code Execution bug in Word itself rather than an elevation of privilege issue, and it carries the lowest CVSS score in this entire set at 7.8 along with a minimal 1 percent EPSS exploit probability, affecting SharePoint Enterprise Server 2016, SharePoint Server 2019, and 32-bit Office 2019. Word RCE bugs are typically triggered by opening a malicious document, so email and file-sharing hygiene matter as much as the patch itself. No confirmed exploitation or ransomware activity.

Do this: Patch Office 2019 and the affected SharePoint versions in the normal cycle, and remind users to be cautious opening unexpected Word attachments in the meantime.

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

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

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-62555 (source: https://senserva.com/cve/CVE-2025-62555.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-62555: High severity Microsoft vulnerability, CVSS 7.0
- EPSS 30-day exploitation probability: <1%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002802, KB5002804, KB5002806, KB5002816, KB5002821
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 KB5002802 and 4 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-62555

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5002802, KB5002804, KB5002806, KB5002816, KB5002821 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-62555. 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.

KB5002802 KB5002804 KB5002806 KB5002816 KB5002821

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-62558 CVE-2025-62559 CVE-2025-62562

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.