Patch tracker / KB5002892
KB5002892: Microsoft SharePoint Server 2019 Security Update (July 2026)
KB5002892 is a High security update for Microsoft SharePoint Server 2019, released 2026-07-14. It closes 22 CVEs with a maximum CVSS of 8.4. The most likely of them to be attacked is CVE-2026-55023, which FIRST.org rates at 77% probability of exploitation in the next 30 days.
Update summary
Fixes 22 CVEs. Most severe CVSS 8.4 (High). EPSS exploit probability up to <1%. Among the lower half of tracked Microsoft updates by EPSS exploit probability.
A newer security update for Microsoft SharePoint Enterprise Server 2016 has shipped since this one: KB5002882 (2026-08-11). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.
Microsoft documents 1 known issue with this update.
- Customers in multi-front-end SharePoint farms with Trusted Provider or Forms authentication may face repeated authentication prompts or multiple...
KB5002892 is a Security Update for SharePoint Enterprise Server 2016 in the July 2026 Patch Tuesday cycle, but Microsoft has not yet published the per-update CVE detail, so its exact fixes and severity remain provisional. On-premises SharePoint 2016 farms are the exposed surface here, and SharePoint has repeatedly been a target for authenticated and pre-auth server-side flaws that lead to remote code execution. The release document maps no named zero-days to this update, so you can plan a normal test-and-deploy window rather than an emergency rollout.
Do this: Stage KB5002892 on a non-production SharePoint 2016 farm to validate services and custom solutions, and check MSRC again once the per-update CVE detail is published before broad deployment.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5002892
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5002892
- Released
- 2026-07-14
- Last changed
- 2026-07-14
- Changes tracked
- 1
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.
Check if KB5002892 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5002892 (checked 2026-08-12). Verify against the article before acting.
Customers in multi-front-end SharePoint farms with Trusted Provider or Forms authentication may face repeated authentication prompts or multiple sign-ins. This should not impact customers who have configured farms with Windows authentication. As a mitigation, configuring sticky sessions on the reverse proxy will address the majority of scenarios. Microsoft is working on a fix in the subsequent product update. While disabling SessionCookieTransformProtectionEnabled may appear to work around the issue, Microsoft does not recommend it. This setting safeguards authentication and turning it off can expose the farm to security vulnerabilities.
When a workflow status link is selected, WrkStat.aspx displays the following error message:
The WorkflowInstanceID parameter is invalid.
To workaround this issue, see Workflow status links fail after installing the July 2026 CU.
Customers who install the SharePoint 2016 July Public Update might find that Office Online Server can't render or edit documents. To mitigate this problem, register the farm's STS signing certificate (public key only) as a trusted token issuer, and then recycle IIS on every server in the farm by using the following steps:
# Get STS certificate
$stsm = Get-SPSecurityTokenServiceConfig
$live = $stsm.LocalLoginProvider.SigningCertificate
# Export public certificate only (without private key)
$bytes = $live.Export("Cert") ...
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-2026-55045 | High | 8.4 | 77% | No |
| CVE-2026-55032 | High | 7.8 | 77% | No |
| CVE-2026-55033 | High | 7.8 | 77% | No |
| CVE-2026-55038 | High | 7.8 | 77% | No |
| CVE-2026-55055 | High | 7.8 | 77% | No |
| CVE-2026-55125 | High | 7.8 | 77% | No |
| CVE-2026-55127 | High | 7.8 | 77% | No |
| CVE-2026-55128 | High | 7.8 | 77% | No |
| CVE-2026-55130 | High | 7.8 | 77% | No |
| CVE-2026-55132 | High | 7.8 | 77% | No |
| CVE-2026-55134 | High | 7.8 | 77% | No |
| CVE-2026-55026 | Medium | 6.2 | 77% | No |
| CVE-2026-55023 | Medium | 5.5 | 77% | No |
| CVE-2026-55027 | Medium | 5.5 | 77% | No |
| CVE-2026-55028 | Medium | 5.5 | 77% | No |
| CVE-2026-55035 | Medium | 5.5 | 77% | No |
| CVE-2026-55047 | Medium | 5.5 | 77% | No |
| CVE-2026-55050 | Medium | 5.5 | 77% | No |
| CVE-2026-55121 | Medium | 5.5 | 77% | No |
| CVE-2026-55124 | Medium | 5.5 | 77% | No |
| CVE-2026-55142 | Medium | 5.5 | 77% | No |
| CVE-2026-56192 | Medium | 5.5 | 77% | No |
Scope and sources
- Affected products
- Also released in July 2026
KB5099444
185 CVEs · Critical · exploitedKB5099445
174 CVEs · Critical · exploitedKB5099535
261 CVEs · Critical · exploitedKB5099536
389 CVEs · Critical · exploitedKB5099538
312 CVEs · Critical · exploitedKB5099539
314 CVEs · Critical · exploitedKB5099540
326 CVEs · Critical · exploitedKB5101649
383 CVEs · Critical · exploitedThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.