Microsoft has used some of its bluntest language yet about old on-premises mail servers. In the November 2026 Exchange Server security update announcement, dated November 10, the Exchange team said the new fixes ship only for Exchange Server Subscription Edition (SE). It then told everyone else this:

"Exchange Server 2016 and 2019 are no longer tested for vulnerabilities and there are no updates released. If you are using those versions of Exchange, you should consider them permanently vulnerable and should upgrade your organization immediately."

Plenty of products reach end of support. What stands out here is the wording. Microsoft isn't just saying it has stopped shipping patches for 2016 and 2019. It says it has stopped testing them for vulnerabilities. Any flaw found in the current Subscription Edition code from now on may or may not also exist in those older versions, and Microsoft says it is not checking.

How Exchange 2016 and 2019 reached this point

The end has been dragged out. As The Register recounts, support for Exchange 2016 and 2019 ended on October 14, 2025. In July 2025 Microsoft announced an Extended Security Updates (ESU) program to keep patches coming for paying customers until April 14, 2026, and said the period "will not be extended past April 2026." It was extended anyway. Microsoft offered another six months, and the last security updates for 2016 and 2019 shipped on October 13.

November 2026 is therefore the first Patch Tuesday cycle with no safety net for those versions. According to The Register, which cites Microsoft's Security Update Guide, this month's release fixes nine vulnerabilities in Exchange SE. Microsoft's post says no updates are released for 2016 or 2019.

The headline bug: CVE-2026-118207

The most serious flaw in this batch is CVE-2026-118207, which The Register describes as a critical remote code execution (RCE) bug. RCE means an attacker can run their own code on the server. According to the National Vulnerability Database record, it is an improper input validation flaw: Exchange doesn't properly validate some of the input it receives. That gap lets an authorized attacker execute code over a network.

The NVD record gives it a CVSS 3.1 score of 8.8, which falls in the High band rather than Critical. The scoring vector explains the number:

  • Network attack vector, low complexity. The attack can be carried out remotely, with no unusual conditions required.
  • Low privileges required. The attacker needs some form of valid access first. That requirement is what keeps the score below 9.0.
  • No user interaction. Nobody has to click anything for the attack to work.

The record lists Exchange Server Subscription Edition RTM builds below 15.02.2562.057 as affected and tags the weakness as CWE-706 (use of an incorrectly resolved name or reference). NVD itself still shows the entry as "Awaiting Analysis." The record also carries a CISA SSVC assessment, a decision-support rating used to prioritize patching, timestamped November 10, with these values:

  • Exploitation: none, meaning no known exploitation was recorded.
  • Automatable: no.
  • Technical impact: "total."

The Register calls the flaw critical, while the NVD record shows a High 8.8 base score. Microsoft's severity label and the CVSS number are separate measures and do not always match. Either way, the practical advice is the same: patch it promptly.

The 2016 and 2019 problem matters most here. The NVD record lists only Subscription Edition as affected, and Microsoft says it no longer tests the older versions. The absence of 2016 and 2019 from the list therefore says nothing about whether they are exposed. Microsoft's statement is explicit: those versions are "no longer tested."

A fix for the October Windows breakage, too

The release also addresses last month's problem. The Register reports that a Windows Server update broke Exchange in the final weeks of the extended support period. Microsoft's post says that installing the November 2026 Windows Server updates resolves the Exchange instability caused by the October Windows updates. Admins who created Microsoft's October registry key can leave it in place, but it is no longer required once the November Windows updates are installed. Microsoft also says the order of installing the Exchange and Windows updates does not matter.

What It Means for Defenders

If you run Exchange Server Subscription Edition: install the November 2026 security update. The NVD record lists SE RTM builds below 15.02.2562.057 as vulnerable to CVE-2026-118207. Microsoft's post adds these points:

  • Patch every on-premises Exchange server, including hybrid management-only servers. Exchange Online customers are already protected on Microsoft's side. A server kept on-site only for management purposes still needs the update.
  • The updates are cumulative. If you are running a cumulative update the security update supports, you don't need to install earlier security updates first.
  • Reboot after setup and confirm Exchange services have started. Microsoft also points admins to its Exchange Health Checker script to find servers that are behind on updates.
  • Watch the auth certificate in hybrid environments. If you change the Exchange authentication certificate after installing a security update, Microsoft says to re-run the Hybrid Configuration Wizard.
  • Install the November Windows Server updates as well. They resolve the Exchange instability from the October Windows patches. The October registry key becomes optional.

If you still run Exchange 2016 or 2019: no patch is coming. The final security updates shipped October 13, and Microsoft's guidance is to upgrade "immediately." The sources give no mitigation that makes these versions safe. Until you finish migrating, use these measures to reduce risk, not to fix it:

  • Make sure the October 13 final updates are installed. Treat the server as a high-risk asset and stop thinking of it as routine infrastructure.
  • Prioritize the migration to Subscription Edition or Exchange Online. Budget and schedule it as security work, not an IT refresh.
  • Because CVE-2026-118207 is described as requiring an authorized attacker, protect the credentials that can reach Exchange. Phishing-resistant sign-in and prompt account lockdowns are sensible precautions for any mail system.
  • Keep these servers off the open internet wherever business needs allow, and monitor them closely.

For federal contractors working through CMMC: in our view, a system the vendor itself calls "permanently vulnerable" will be hard to defend in an assessment. Any unsupported Exchange server that handles controlled information belongs at the top of your remediation plan, with a dated migration path documented.

The takeaway is simple. Microsoft extended the deadline once, after saying it wouldn't, and it is now finished with 2016 and 2019. Anyone still running those versions is betting that no new flaw found in SE exists in the older code, and with Microsoft no longer testing those versions, nobody is positioned to tell them otherwise.

Sources