KB5121573: Security update for Exchange Server Subscription Edition RTM, August 2026. Exchange privilege flaw addressed; published calendar feeds can fail
A critical Exchange privilege-escalation flaw is addressed. Published calendar subscriptions might stop refreshing and return HTTP 500.
Does it affect you? Applies to: Exchange Server Subscription Edition RTM, x64, build 15.2.2562.46.
Review notes Additional details from the official release notes (2) Read notes
- In short After installing this update, subscriptions to anonymously published Exchange calendars stop refreshing, and the calendar URL returns HTTP 500.
- Known issues After installing this update, subscriptions to anonymously published Exchange calendars stop refreshing, and the URL returns an HTTP 500 server error.
The official sources are linked at the end of the page.
What changes
Fix 1 change
Exchange Server
-
The update addresses a critical flaw that could let an attacker gain higher privileges in Exchange Server.1
CVE-2026-62911 is an elevation-of-privilege vulnerability.
Known issues
-
Published calendar (.ics) returns HTTP 500 for calendar applications
After this update, subscriptions to anonymously published Exchange calendars might stop refreshing. Calendar apps might receive an HTTP 500 error.2
How to apply the workaround IIS / URL RewriteAdd a URL Rewrite rule to the Exchange Back End site. It adds
layout=premiumto calendar-feed requests that do not already have a layout parameter.2Step-by-step workaround instructionsShow steps Hide steps5 stepsStep-by-step procedure- Confirm that the IIS URL Rewrite module is installed.
- In IIS Manager, add a blank inbound rule to the Exchange Back End site's URL Rewrite settings.
- Match
^owa/calendar/.+\.ics$and add a condition that excludes requests whose query string already containslayout=. - Rewrite the URL to
{R:0}?layout=premium&{QUERY_STRING}; clear Append query string. - Apply the rule on every server that serves the published calendar. No application pool recycle is required.
-
Availability (free/busy) fails for delegated mailboxes in Exchange hybrid deployments using Graph API only
In some Exchange hybrid setups, checking a delegated mailbox's availability might show an error or no details. This affects Graph API-only setups; Microsoft says the service fix is available.3
How to apply the workaround Exchange Management ShellThe override enables the Graph API route for availability checks. Refreshing Variant Configuration applies the change immediately.3
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit3 steps Exchange Management Shell Instructions (.txt)Step-by-step procedure- Check the current value of the override.
- Only if it is
Enabled=Falseor was previously disabled, set it toEnabled=True. - Run the refresh command to apply the change immediately.
> Get-SettingOverride -Identity EnableRouteThroughMSGraphFeature> Set-SettingOverride -Identity EnableRouteThroughMSGraphFeature -Parameters "Enabled=True"> Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh
-
Wrapper messages appear in shared mailbox in hybrid environments after installing the June 2026 Security Update
In Exchange hybrid, sent messages might appear as attachments in an Exchange Online shared mailbox Inbox. With an on-premises sender, Send As or Send on Behalf rights, and message-copy enabled, this occurs; KB5121608 resolves it.4
How to apply the workaround Exchange Management ShellThe article says to remove the override if it was created as a workaround for this issue.4
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit2 steps Exchange Management Shell Instructions (.txt)Step-by-step procedure- In Exchange Management Shell, check whether the override exists.
- If it exists, remove it.
> Get-SettingOverride "DisableBlockSharedAndUserMailboxHeaders"> Remove-SettingOverride "DisableBlockSharedAndUserMailboxHeaders"
Technical details
Data sheet · Security · Downloads · Components Click to collapse or expand
Data sheet
- Released
- 2026-08-11
- Classification
- Security Updates
- Type
- Cumulative update
- Servicing branch
- RTM
- Replaces
- KB5103212, KB5094139
- Replaced by
- KB5121608
| Version | Build | Channel |
|---|---|---|
| SE | 15.2.2562.46 | General availability |
Security
| Vulnerability | Severity | CVSS |
|---|---|---|
|
Microsoft Exchange Server Elevation of Privilege Vulnerability
|
Critical | 8.0 |
|
Microsoft Exchange Server Remote Code Execution Vulnerability
|
Important | 8.8 |
|
Microsoft Exchange Server Spoofing Vulnerability
|
Important | 7.3 |
|
Microsoft Exchange Server Elevation of Privilege Vulnerability
|
Important | 7.2 |
|
Microsoft Exchange Server Denial of Service Vulnerability
|
Important | 6.5 |
|
Microsoft Exchange Server Security Feature Bypass Vulnerability
|
Important | 6.5 |
|
Microsoft Exchange Server Elevation of Privilege Vulnerability
|
Important | 6.5 |
Downloads (Microsoft Update Catalog)
Updated components
1,004 files changed since the previous update for the same versions.
| Top changed components | Files |
|---|---|
| Management and PowerShell | 123 |
| Transport | 93 |
| Client access (POP, IMAP, ActiveSync) | 33 |
| Mailbox replication | 33 |
| Search | 27 |
| Compliance and eDiscovery | 24 |
| Exchange Web Services and Autodiscover | 17 |
| Outlook on the web | 8 |
| Setup | 8 |
Sources
- Microsoft Support: KB5121573
- Microsoft Support: KB5126672
- Microsoft Support: KB5105719
- Microsoft Support: KB5127092
Cited passages from Microsoft's official notes (4)
-
1.
- CVE-2026-62911 - Microsoft Common Vulnerabilities and Exposures
support.microsoft.com -
2.
Add one URL Rewrite rule to the Exchange Back End site in IIS. The rule appends
support.microsoft.comlayout=premiumto .ics requests below /owa/calendar/. -
3.
If it is set to
support.microsoft.comEnabled=False, or if you had previously disabled the override, re-enable it by setting it toEnabled=Trueusing the following command: -
4.
messages that are Sent As, or Sent on Behalf of, the shared mailbox may also be delivered to the Inbox folder of the shared mailbox as attachments
support.microsoft.com
Checked automatically: 8 of 8 checks passed, 4 quoted passages · compared with Microsoft's page on Oct 16, 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: passed
A second AI read the text against the sources: correctness 4/5, clarity 3/5, completeness 5/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