Blog Post

Exchange Team Blog
5 MIN READ

Released: July 2026 Exchange Server Security Updates

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Jul 14, 2026

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:

The July 2026 SUs address vulnerabilities responsibly reported to Microsoft by security partners and found through Microsoft’s internal processes.

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).

Check for presence of legacy Exchange security groups

While not directly related to our July 2026 SU release, we wanted to call out that Exchange Health Checker script will now also check for the presence of very old, deprecated Exchange Server security groups, namely Exchange Domain Servers and Exchange Enterprise Servers. Those groups have been deprecated since Exchange 2007, should not be in use, and should be deleted as they might provide more permissions than modern Exchange security groups. Please see related documentation here.

Customers who have removed last on-premises Exchange Server from their organizations should also check for the presence of those groups and delete them to help prevent their possible abuse. Note that if you no longer have any Exchange servers on premises, you might want to perform a more comprehensive Active Directory cleanup as per this article.

Remove CVE-2026-42897 mitigations after installation

Installing the July 2026 update does not automatically remove already applied CVE-2026-42897 mitigations. Therefore, once you install July SU, you should:

If mitigation was applied using Exchange Emergency Mitigation (EM) Service:

If mitigation was applied using the downloadable EOMT script https://aka.ms/UnifiedEOMT:

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

Update installation

The following update paths are available:

FAQs

When CVE-2026-42897 mitigation was released, there were several reported known issues. Are those addressed in this update?
Yes, when July 2026 SU is installed and mitigation is removed, mitigation known issues should be resolved too.

If we update some of our servers but cannot update others, can servers that will not receive update stay with CVE-2026-42897 mitigations? Is it OK to have some servers updated and some still using mitigations?
You can continue using mitigations on any servers that you cannot update to July 2026 SU (or newer). But note that known issues from mitigations will continue to apply to those servers. Additionally, after applying this update, Office Online Server (OOS) integration with Exchange Server might not function as expected until all Exchange servers in the organization have been updated.

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.

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.

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

Updated Jul 24, 2026
Version 2.0

45 Comments

  • ManleyDOA's avatar
    ManleyDOA
    Brass Contributor

    In the "Rollback procedures for released mitigations" section on this page: https://learn.microsoft.com/en-us/Exchange/plan-and-deploy/post-installation-tasks/security-best-practices/exchange-emergency-mitigation-service#rollback-procedures-for-released-mitigations 

    Why is the header called M2 when the mitigation applied is called M2.1.0 ?

    MitigationsApplied : {PING1, M2.1.0}

    • Nino_Bilic's avatar
      Nino_Bilic
      Icon for Microsoft rankMicrosoft

      Mitigations could have "versions" or "revisions" hence the numbers after "2". In this case, that did not really get used (but the capability is there) but when working with the specific mitigation it needs to be referenced specifically. So we would not use "M2.anything" for a different mitigation if we needed to release one let's say next year (or whatever) it would be M3.something.

  • ManleyDOA's avatar
    ManleyDOA
    Brass Contributor

    If the EM service can automatically apply the M2.1.0 mitigation, why can it not automatically remove it after confirming July SU installed?

    • Nino_Bilic's avatar
      Nino_Bilic
      Icon for Microsoft rankMicrosoft

      The service was not designed to remove mitigations that are IIS rules; that could have been done differently, of course. There is more risk trying to remove stuff automatically, and seeing that customers could have other rules on IIS and we really try not to release mitigations unless in emergency, it lead to where we are today. It is a reasonable question.

  • FrankWest's avatar
    FrankWest
    Tin Contributor

    One of our servers had it's Exchange services still set to disabled. The script to recover these after the patch didn't help. I got warnings like this:

    WARNING: 'MSExchangeIS' did not exist, this is not an error as the sevice might have just been installed

    WARNING: 'MSExchangeMailboxAssistants' did not exist, this is not an error as the sevice might have just been installed

    WARNING: 'MSExchangeMailboxReplication' did not exist, this is not an error as the sevice might have just been installed

    They did exist and I had to manually enable them (as well as the dependent Windows services). Server is functioning now, but how can I be sure that the update was installed successfully? And why weren't the services set to automatic again after the install?

  • PeteG2400's avatar
    PeteG2400
    Copper Contributor

    despite rebooting the server before applying this update and putting exchange in maintenance mode, the install wasn't happy because it couldn't update various files because various services (some of them Exchange, some of them other Microsoft services like WMI and Remote Registry) were still in use. Painful!

  • Thomas-G's avatar
    Thomas-G
    Copper Contributor

    I have installed the SU in a couple of lab servers for testing, when I run "EOMT.ps1 -ShowMitigationStatus -CVE "CVE-2026-42897"", I get the following result:

    Checking mitigation status for CVE-2026-42897 on EXCH*****
    EXCH***** : Code Fix Applied: False | Mitigation Applied: True

    Since removing the mitigation is the the indicated last step, and based on the first FAQ, I would have thought it would show "Code Fix Applied: True".

    Am I wrong in thinking that the SU included a code fix that the mitigation was for?

     

    • Nino_Bilic's avatar
      Nino_Bilic
      Icon for Microsoft rankMicrosoft

      You are right, it appears that we missed to update EOMT to treat July SU as the build that has a "code fix". We'll take care of it.

      (You are welcome to remove the EOMT applied mitigation anyway, though)

  • Pankaj9873's avatar
    Pankaj9873
    Brass Contributor

    Nino_Bilic​ Hello, Do we still need to remove M2 mitigation, after July SU installation? my organization dont see any issue because we do not have any mailboxes on Exchange Server.

     

    • Nino_Bilic's avatar
      Nino_Bilic
      Icon for Microsoft rankMicrosoft

      You do not need to remove the mitigation if you do not host mailboxes on premises. You can. But you do not need to as the mitigation will not break anything.

      But for those who host mailboxes on-prem, yes - they need to remove the mitigation after installation of July 2026 SU.

      • gstv's avatar
        gstv
        Copper Contributor

        Nino_Bilic​  Hi, we have just installed the July SU (on-prem) and after running "Get-Mitigations.ps1" and the "Exchange Health Checker", we only get the following result:

        Mitigation appliedPING1

        Before the installallation of July SU, the output of those scripts was:

        Mitigation appliedPING1
        Mitigation appliedM2.1.0

        Does that mean that the mitigation has been automatically removed after installing the July SU? We had understood from the reading of this thread that this wasn't the case and that it had to be done “manually.”

  • In regards to the Legacy Exchange Security Groups, as I still had Exchange Domain Servers hanging around, I see the script detects it from the output XML plus see it listed when run in verbose mode but doesn't mention their presence in the associatext TXT output file from the HealthChecker script ? Maybe by design by thought worth mentioning,. 

  • SerafinG's avatar
    SerafinG
    Copper Contributor

    In the KB article (KB5103212), the links to the 3 last CVEs are pointing to 2025 instead of 2026.  They will show up as 404s,
    They should point to 
    https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55006
    https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55008
    https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55009