Microsoft has released Security Updates (SUs) for vulnerabilities found in:
- Exchange Server Subscription Edition (SE)
- Exchange Server 2019
- Exchange Server 2016
SUs are available for the following specific versions of Exchange Server:
- Exchange SE RTM
- Exchange Server 2019 CU14 and CU15 (to access, organization must be enrolled into the Period 2 ESU program)
- Exchange Server 2016 CU23 (to access, organization must be enrolled into the Period 2 ESU program)
The September 2026 V2 SUs address vulnerabilities responsibly reported to Microsoft by security partners and found through Microsoft’s internal processes.
The difference between the original September 2026 Security Update release and this V2 release is an addition of CVE-2026-96940. Please see the download KB article for more information.
These vulnerabilities affect Exchange Server. Exchange Online customers are already protected from the vulnerabilities addressed by these SUs and do not need to take any action other than updating any Exchange servers or Exchange Management tools workstations in their environment.
More details about specific CVEs can be found in the Security Update Guide (filter on ‘Server Software’ under Product Family for Exchange SE and ‘ESU’ under Product Family for Exchange 2016 and 2019).
Exchange 2016 and 2019 updates are available only under the Period 2 ESU program
Exchange Server 2016 and 2019 are out of support. Only customers who enrolled in the Period 2 Extended Security Update (ESU) program are eligible to receive Exchange Server 2016 and 2019 security updates released between May and October 2026.
If you are not part of the Period 2 ESU program, migrate to Exchange Server Subscription Edition (SE) to keep receiving the latest security updates.
If you have already purchased the Period 2 ESU and need information on accessing the latest Security Updates, please contact us by sending an email to ExchangeandSfBServerESUInquiry@service.microsoft.com.
Known issues with this release
- Published calendar (.ics) returns HTTP 500 for calendar applications | Microsoft Support – to be resolved in a future update
- ContentEngine deadlock because of missing Korean WordBreaker rule files | Microsoft Support – an issue impacting customers with emails in Korean language, to be addressed in a future update
Issues resolved in this release
- Wrapper messages appear in shared mailbox inbox in hybrid environments | Microsoft Support
- Availability (free/busy) fails for delegated mailboxes in Exchange hybrid deployments using Graph API only | Microsoft Support
Update installation
The following update paths are available:
- Inventory your Exchange Servers to determine which updates are needed using the Exchange Server Health Checker script. Running this script will tell you if any of your Exchange Servers are behind on updates (CUs, SUs, or manual actions).
- Install the latest CU. Use the Exchange Update Wizard to choose your current CU and your target CU to get directions.
- After setup is completed, please reboot the server and check that all Exchange services have started properly. If some services are in a disabled state, that indicates that something interrupted installation of the update. Please see the Workaround 1 in this article.
- If you encounter errors during or after installation of Exchange Server, run the SetupAssist script. If something does not work properly after updates, see Repair failed installations of Exchange Cumulative and Security updates. Also please see File version error when you try to install Exchange Server updates.
FAQs
Our organization is in Hybrid mode with Exchange Online. Do we need to do anything?
Exchange Online is already protected, but this SU needs to be installed on your Exchange servers, even if they are used only for management purposes. If you change the auth certificate after installing an SU, you should re-run the Hybrid Configuration Wizard.
The last SU/HU we installed is a few months old. Do we need to install all SUs in order to install the latest one?
SUs are cumulative. If you are running a CU supported by the SU, you do not need to install all SUs or HUs in sequential order; simply install the latest SU. Please see this blog post for more information.
Do we need to install SUs on all Exchange Servers within our organization? What about ‘Management Tools only’ machines?
Our recommendation is to install SUs on all Exchange Servers and all servers and workstations running the Exchange Management Tools to ensure compatibility between management tools clients and servers. If you are trying to update the Exchange Management Tools in the environment with no running Exchange servers, please see this.
We installed an Exchange SU or HU update and are running Windows Server 2025. How do we uninstall updates as they are not listed on Windows Server 2025?
We do not recommend uninstalling Security Updates. But see Can't view or uninstall Exchange security or hotfix updates in Control Panel on Windows Server 2025 | Microsoft Support.
Our organization does not have the Exchange 2016 and 2019 Period 2 ESU. How can we get current Exchange 2016 or 2019 updates?
Since Exchange 2016 and 2019 are now out of support, only customers who have enrolled into the Period 2 ESU program (which is valid between May and October 2026) can obtain Exchange 2016 or 2019 updates released after May 2026. For all other customers still running Exchange 2016 or 2019, we recommend that you upgrade your organization to Exchange SE as soon as possible.
The release sequence of this specific update was a bit strange. Why is this?
This specific update, which adds CVE-2026-96940, was published ahead of its intended schedule. We recommend that customers review the deployment guidance and apply the update at the earliest opportunity.
- We identified the vulnerability internally and are not aware of active exploitation.
- For information about additional updates, customers should refer to our established security update channels.
Documentation may not be fully available at the time this post is published.
This post might receive future updates; they will be listed here (if available).
The Exchange Server Team
