Patch tracker / CVE reference / CVE-2025-59235

CVE-2025-59235

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

Risk summary

High

7.1

CVSS v3

2.3%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.3%. CVSS 7.1 (High).

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

Senserva AI Opinion for CVE-2025-59235

This Excel information-disclosure flaw is scored higher at 8.8 and notably also reaches SharePoint Server 2016 and 2019 alongside Office Online Server, widening its footprint into collaboration platforms. The 2 percent EPSS is low, but the SharePoint overlap means server administrators, not just endpoint teams, need to act. Excel content rendered server-side is the shared exposure.

Do this: Patch Office Online Server plus SharePoint 2016 and 2019 for CVE-2025-59235, coordinating across endpoint and SharePoint teams.

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

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

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-59235 (source: https://senserva.com/cve/CVE-2025-59235.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-59235: High severity Microsoft vulnerability, CVSS 7.1
- EPSS 30-day exploitation probability: 2.3%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002341, KB5002719, KB5002720, KB5002757, KB5002788, KB5002794, KB5002796, KB5002797
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 2%.

Fixed by KB5002341 and 7 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-59235

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5002341, KB5002719, KB5002720, KB5002757, KB5002788, KB5002794, KB5002796, KB5002797 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-59235. 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.

KB5002341 KB5002719 KB5002720 KB5002757 KB5002788 KB5002794 KB5002796 KB5002797

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-59228 CVE-2025-59237 CVE-2025-59236 CVE-2025-59222 CVE-2025-59223 CVE-2025-59224 CVE-2025-59225 CVE-2025-59231

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.