Patch tracker / KB5002754
KB5002754: Microsoft SharePoint Server 2019 Security Update (July 2025)
KB5002754 is a Critical security update for Microsoft SharePoint Server 2019, released 2025-07-08. It closes 2 CVEs with a maximum CVSS of 9.8. At least one of them is actively exploited (CISA KEV) and linked to ransomware, so this is a deploy-first update. Get it from the Microsoft Update Catalog below, and see where it sits against the rest of the month on the patch tracker.
Microsoft security update released 2025-07-08. Fixes 2 CVEs.
Exploitation is not theoretical here: at least one CVE this update fixes is on the CISA Known Exploited Vulnerabilities catalog, which means attackers are already using it against unpatched systems, including in ransomware campaigns. For an update like this, the risk window is the gap between today and the day your last device installs it, so shortening that gap matters more than perfect scheduling.
Most organizations deliver an update like this automatically through Intune update rings, Windows Update for Business, Windows Autopatch, or WSUS; the install section below covers each path, including how to expedite it for the exploited CVE. For the bigger picture: how the Microsoft patching tools fit together, this month's Patch Tuesday summary, and every update ranked by real-world risk.
Updated July 23, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Download KB5002754
Get the official update for KB5002754. The download and file size for each supported product are on the Microsoft Update Catalog page.
Update summary
Senserva AI Opinion for KB5002754
KB5002754 patches two SharePoint on-premises flaws, including CVE-2025-53770, that carry a Critical CVSS 9.8 rating, sit at 100 percent EPSS, and are already in CISA KEV with confirmed ransomware use. Anyone running SharePoint Enterprise Server 2016, Server 2019, or Subscription Edition on-premises is exposed, and these are the ToolShell chain vulnerabilities being actively exploited to breach SharePoint farms. This is not a wait-and-test situation because working exploitation is public and tied to ransomware operators.
Do this: Apply KB5002754 to all on-premises SharePoint 2016, 2019, and Subscription Edition servers immediately, rotate ASP.NET machine keys, and hunt for signs of prior compromise.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5002754
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5002754
Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.
Exploitation and severity
Fixes 2 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 100%. One is linked to ransomware.
Among the top 5% of tracked Microsoft updates by EPSS exploit probability.
What to do
Treat as urgent: it is being exploited in the wild (CISA KEV), so patch ahead of items that are not. Senserva flags whether KB5002754 is missing on your devices.
Check if KB5002754 is installed
Copy-paste PowerShell: one machine, or your whole fleet in one pass. No output means the update is not installed.
Get-HotFix covers Windows updates. Office, SharePoint, and Exchange server updates show under installed updates in Programs and Features, or check the Update Catalog history.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5002754 (checked 2026-07-22). Verify against the article before acting.
Users may experience an issue when loading some SharePoint page resources, and the following error message is logged in the SharePoint Unified Logging System (ULS) logs:
Note
[SPRequestModule.PostAuthenticateRequestHandler] Risky signout bypass limited (Access Denied). request path: '<resource path>'.
To work around this issue, farm administrators can add the resource path in the AllowList by running the following PowerShell commands:
$farm = get-spfarm
$farm.AddGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")
$farm.Update()
iisreset
To check whether the resource path exists in the AllowList, run:
$farm.ContainsGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")
To remove the resource path from the AllowList, run:
$farm.RemoveGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")
Note
Make sure that the resource path is valid and as expected before you follow the instructions to configure it.
Writing about KB5002754? Cite this page
Copy-paste for a blog post, forum answer, or internal doc. The link always carries the current risk data.
CVEs fixed by this update
Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.
| CVE | Severity | CVSS | EPSS | Exploited |
|---|---|---|---|---|
| CVE-2025-53770 | Critical | 9.8 | 100% | KEV Ransomware |
| CVE-2025-53771 | Critical | 9.8 | 100% | No |
What the press says about this update
Trusted-source coverage of the CVEs this update fixes, pulled live from their own feeds.
Affected products
Also released in July 2025
The highest-risk updates from the same release:
The full month, summarized: Microsoft Patch Tuesday.
How to install KB5002754
Any of these paths delivers KB5002754; most organizations already have one of the first three running:
- Intune update rings (Windows Update for Business): the update flows on each ring's deferral schedule. For this update, consider an expedite policy: it bypasses deferrals for exactly this fix-now case.
- Windows Autopatch: rings, rollout, and pause or rollback are managed for you; exploited updates can be expedited.
- WSUS / Configuration Manager: approve KB5002754 for your device groups and set a deadline (deadline, not just approval, for an exploited fix).
- Manual: download from the Update Catalog above and install; fine for a handful of machines, unmanageable at any real scale.
After the rollout, verify rather than assume: update compliance reporting in Intune or Autopatch shows which devices actually installed it, and Siemserva reads Intune, Defender, Autopatch, and Azure Update Manager together to show the devices still missing KB5002754, ranked by exploitation.
Common questions about KB5002754
Does KB5002754 have known issues?
Yes. Microsoft's support article documents known issues for KB5002754 (checked 2026-07-22). The Known issues section on this page quotes it; verify against the article before acting.
Is KB5002754 urgent?
Yes. KB5002754 fixes at least one vulnerability in the CISA Known Exploited Vulnerabilities catalog, meaning attackers are using it in the wild, including in ransomware campaigns. Deploy it first.
How do I download KB5002754?
From the Microsoft Update Catalog (linked on this page), or let Intune, Windows Update for Business, Windows Autopatch, or WSUS deliver it. The catalog page lists the download for each supported product.
How do I deploy KB5002754 with Intune?
Assign a Windows Update ring (quality update policy) to the device groups and the update flows on the ring's deferral schedule. Because KB5002754 fixes an actively exploited CVE, an Intune expedite policy is the right tool: it bypasses configured deferrals and pushes the update as soon as devices check in. Verify the rollout with update compliance reporting rather than assuming delivery.
Can I ask my own AI about KB5002754?
Yes. This page includes a free, ready-to-paste AI prompt containing KB5002754's key facts: severity, CVE count, exploitation status, and the download link. Copy it into Claude, ChatGPT, or Copilot for a rollout plan; the data is refreshed three times a day (5 AM, 12:30 PM, and 7 PM US Central).
Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.
