KB5002883: Cumulative update for SharePoint Server, version 2019, July 2026. Exploited privilege flaw patched; workflow and page fixes
An actively exploited privilege flaw is patched, alongside fixes for page loading and SharePoint 2010 workflows. Support for version 2019 ends on July 14, 2026.
Does it affect you? Applies to: SharePoint Server 2019 farms running the release version. The update package advances the build to 16.0.10417.20175.
Review notes Additional details from the official release notes (1) Read note
- In short The dossier records that updates for all SharePoint Server 2019 editions ended on July 14, 2026; it does not establish that product support ended that day.
The official sources are linked at the end of the page.
Microsoft ships this release as two packages: KB5002883, the update itself, and KB5002885 for the language packs. Install both on every server of the farm, then run the SharePoint Products Configuration Wizard.
What changes
Fixes 2 changes
SharePoint pages
-
Pages can load when certain user controls were flagged as unsafe for security.1
You can explicitly trust the affected controls by configuring the custom farm property
AllowedTagPrefixesWhichAreNotWebControlsList.
SharePoint 2010 workflows
- SharePoint 2010 workflows can start after the June 2026 update is installed.2
Known issues
-
Customers in multi-front-end SharePoint farms with Trusted Provider or Forms authentication may face repeated authentication prompts or multiple sign-ins.
Users in multi-front-end farms using Trusted Provider or Forms authentication may see repeated authentication prompts or multiple sign-ins. This should not impact farms using Windows authentication.3
How to apply the workaround WorkaroundConfigure sticky sessions on the reverse proxy; this addresses most scenarios.3
-
When a workflow status link is selected, WrkStat.aspx displays the following error message: The WorkflowInstanceID parameter is invalid.
Selecting a workflow status link can show an error that says the WorkflowInstanceID parameter is invalid.4
How to apply the workaround WorkaroundFollow the linked guidance for workflow status links.4
Technical details
Data sheet · Security · Downloads · Components Click to collapse or expand
Data sheet
- Released
- 2026-07-14
- Classification
- Security Updates
- Type
- Cumulative update
- Restart
- Required
- Replaces
- KB5002874, KB5002870, KB5002854, KB5002845
- Replaced by
- KB5002894
| Version | Build | Channel |
|---|---|---|
| 2019 | 16.0.10417.20175 | General availability |
Security
| Vulnerability | Severity | CVSS |
|---|---|---|
|
CVE-2026-56164
Exploited
Microsoft SharePoint Server Elevation of Privilege Vulnerability
|
Moderate | 5.3 |
|
Microsoft SharePoint Remote Code Execution Vulnerability
|
Critical | 9.8 |
|
Microsoft SharePoint Server Security Feature Bypass Vulnerability
|
Critical | 9.1 |
|
Microsoft Office Remote Code Execution Vulnerability
|
Critical | 8.4 |
|
Microsoft Word Remote Code Execution Vulnerability
|
Critical | 7.8 |
|
Microsoft Word Remote Code Execution Vulnerability
|
Critical | 7.8 |
|
Microsoft Word Remote Code Execution Vulnerability
|
Critical | 7.8 |
The table lists the 7 exploited, publicly disclosed or critical vulnerabilities. See all 40 vulnerabilities →
Downloads (Microsoft Update Catalog)
Language packs (50)
- Arabic (Saudi Arabia)
- Azerbaijani (Latin, Azerbaijan)
- Basque (Spain)
- Bosnian (Latin, Bosnia & Herzegovina)
- Bulgarian (Bulgaria)
- Catalan (Spain)
- Chinese (China)
- Chinese (Taiwan)
- Croatian (Croatia)
- Czech (Czechia)
- Danish (Denmark)
- Dari (Afghanistan)
- Dutch (Netherlands)
- English (United States)
- Estonian (Estonia)
- Finnish (Finland)
- French (France)
- Galician (Spain)
- German (Germany)
- Greek (Greece)
- Hebrew (Israel)
- Hindi (India)
- Hungarian (Hungary)
- Indonesian (Indonesia)
- Irish (Ireland)
- Italian (Italy)
- Japanese (Japan)
- Kazakh (Kazakhstan)
- Korean (South Korea)
- Latvian (Latvia)
- Lithuanian (Lithuania)
- Macedonian (North Macedonia)
- Malay (Malaysia)
- Norwegian Bokmål (Norway)
- Polish (Poland)
- Portuguese (Brazil)
- Portuguese (Portugal)
- Romanian (Romania)
- Russian (Russia)
- Serbian (Cyrillic, Serbia)
- Serbian (Latin, Serbia)
- Slovak (Slovakia)
- Slovenian (Slovenia)
- Spanish (Spain)
- Swedish (Sweden)
- Thai (Thailand)
- Turkish (Türkiye)
- Ukrainian (Ukraine)
- Vietnamese (Vietnam)
- Welsh (United Kingdom)
Updated components
453 files changed since the previous update for the same versions.
| Top changed components | Files |
|---|---|
| Search | 44 |
| Project Server | 23 |
| Document conversion | 20 |
| Client object model | 9 |
| Access Services | 8 |
| Document management and policies | 6 |
| Managed metadata | 5 |
| Office web apps | 3 |
| PowerPoint | 3 |
| PowerShell | 2 |
| Publishing | 2 |
| Translation Services | 2 |
Page history
-
Added CVE-2026-97783 (Important)
Sources
Cited passages from Microsoft's official notes (4)
-
1.
Fixes an issue in which pages don't load because certain user controls are flagged as unsafe for security.
support.microsoft.com -
2.
Fixes an issue in which SharePoint 2010 workflows don't initiate after the June 2026 update is installed.
support.microsoft.com -
3.
Customers in multi-front-end SharePoint farms with Trusted Provider or Forms authentication may face repeated authentication prompts or multiple sign-ins.
support.microsoft.com -
4.
To workaround this issue, see Workflow status links fail after installing the July 2026 CU.
support.microsoft.com
Checked automatically: 7 of 8 checks passed, 4 quoted passages · compared with Microsoft's page on Sep 26, 2026
- Quotes found in the official pages: passed
- Numbers found in the sources: passed
- Vulnerabilities from the dossier only: passed
- Links to allowed domains only: passed
- Every official change covered: passed
- Readable plain text: passed
- Changes confirmed by the file list: passed
- Sources agree: not passed
A second AI read the text against the sources: correctness 3/5, clarity 3/5, completeness 4/5. How we work
Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake