Nov 15, 2026 · 8 min read
Exchange 2016 and 2019 Are Now Permanently Vulnerable
The last paid security update for Exchange Server 2016 and 2019 shipped on October 13, 2026. November's Patch Tuesday fixed nine Exchange bugs, including a Critical remote code execution flaw, for Subscription Edition only, and Microsoft has stopped testing or even naming the older versions.
Microsoft rarely tells customers, in writing, that a product it sold them is beyond saving. It did on November 10, 2026. The Exchange team's November 2026 security update post says Exchange Server 2016 and 2019 "are no longer tested for vulnerabilities and there are no updates released," and that anyone still running them "should consider them permanently vulnerable and should upgrade your organization immediately." The Register picked up the line on November 12. For the thousands of organizations that still run their own mail servers, the grace period is over.
Key Takeaways
- Exchange Server 2016 and 2019 reached end of support on October 14, 2025, and the final update under Microsoft's paid Extended Security Update program shipped on October 13, 2026, to paying customers only.
- November 2026 is the first Patch Tuesday with no Exchange 2016 or 2019 fix, while Exchange Server Subscription Edition received patches for nine vulnerabilities, including the Critical remote code execution bug CVE-2026-118207.
- Microsoft says its CVEs "will stop mentioning Exchange 2016 and 2019," so vulnerability scanners that rely on affected product lists will no longer flag new flaws in those versions.
- Shadowserver's most recent public snapshot, from August 31, 2026, counted 21,899 internet exposed Exchange servers unpatched against a single mailbox takeover bug.
- Admins must move to Exchange Server SE or Exchange Online; until then, CISA and NSA guidance says to keep old servers off the public internet and isolated.
What Does Permanently Vulnerable Mean for Exchange?
Permanently vulnerable means Microsoft will neither look for nor fix new security flaws in Exchange 2016 and 2019, so every bug found from now on stays open on those servers forever. That is a stronger statement than "unsupported." Microsoft's October 2026 update post spells out the three parts:
- "Updates will be released for Exchange Subscription Edition (SE) only."
- "Our update announcements and any CVEs released by MSRC will stop mentioning Exchange 2016 and 2019."
- "We will stop testing Exchange 2016 and 2019 for vulnerabilities."
The post adds a warning that is easy to skim past: silence "does not mean that those versions are not vulnerable to future security issues."
How Did Exchange 2016 and 2019 Get Here?
Both versions ran out of support a year ago and survived on two paid extensions that Microsoft said it did not want to sell. The timeline:
- October 14, 2025: Extended support ended for both, per Microsoft's lifecycle pages for Exchange Server 2016 and Exchange Server 2019.
- Period 1 ESU, to April 2026: A six month Extended Security Update program. Microsoft said at the time, as quoted by The Register, "This period will not be extended past April 2026 (you do not need to ask)."
- April 15, 2026: Microsoft extended it anyway. The Period 2 ESU announcement covered May through October 2026 for Enterprise Agreement customers, sold per server, and stated: "We are not committing to actually releasing any SUs during the Period 2 ESU."
- Everyone else: Servers whose owners never bought ESU have had no fixes since October 2025. The October post told "all other customers still running Exchange 2016 or 2019" to upgrade to SE "as soon as possible."
- October 13, 2026: Microsoft "released the final set of updates under the Exchange 2016/2019 ESU program."
- November 10, 2026: The first Patch Tuesday that ships Exchange fixes for SE alone.
Why Is the November Patch the Real Warning Sign?
The November patch matters because it probably fixes code that still exists, unpatched, inside Exchange 2019. Microsoft's Security Update Guide lists CVE-2026-118207 as a Critical remote code execution flaw with a CVSS 3.1 score of 8.8, needing only low privileges and no user interaction. The affected product list names one product: Exchange Server Subscription Edition RTM. Our November 2026 Patch Tuesday breakdown covers it alongside the eight other Exchange fixes that month.
Here is the part the headlines skip. Microsoft's own SE upgrade guide says "Exchange Server SE RTM will be code equivalent to Exchange 2019 CU15." If SE started as a renamed 2019 CU15, a bug Microsoft finds in SE has a good chance of sitting in the same code on 2019. We cannot confirm that for any single CVE, because Microsoft no longer tests the old versions. That is exactly the problem.
The second consequence hits security teams directly. Scanners and asset inventories that match installed software against the affected product entries in each CVE will miss this. The CVE record for CVE-2026-118207 lists only the SE product identifier. A dashboard keyed on those entries will show a 2019 server as clean for this flaw, and every future one. Flag old Exchange as end of life in the inventory itself, not per CVE.
How Many Exchange Servers Are Still Exposed?
No one has published a count of internet facing Exchange 2016 and 2019 servers since the program ended; the latest public data point measures neglect of a single bug instead. On August 31, 2026, the Shadowserver Foundation counted 21,899 internet exposed Exchange servers still unpatched against CVE-2026-62911, a mailbox takeover bug, with about 6,200 in the United States and 5,100 in Germany, BleepingComputer reported. That count mixes 2016, 2019 and SE, so it is a floor for neglect, not an end of life census. We covered that flaw in 21,899 Exchange Servers Still Open to Mailbox Hijack.
Two regional data points sharpen the picture. Germany's BSI warned that about 85% of on premises Exchange servers in the country remained vulnerable, per the same report. iTnews counted 382 vulnerable servers in Australia and 56 in New Zealand, and quoted the Australian Signals Directorate saying legacy technology without updates "are an easy target for malicious actors." Organizations that could not apply a patch which existed are unlikely to complete a full migration in a few weeks.
What Happened the Last Time Exchange Sat Unpatched?
The last time attackers held working Exchange exploits that defenders could not patch, thousands of mail servers were backdoored. On March 2, 2021, Microsoft disclosed HAFNIUM, a China based group chaining four zero days, CVE-2021-26855, CVE-2021-26857, CVE-2021-26858 and CVE-2021-27065, known together as ProxyLogon. The operators dropped web shells, exported mailboxes with Exchange PowerShell and dumped LSASS memory for credentials.
CISA's advisory AA21-062A told admins to hunt for compromise back to January 1, 2021, and to "assume network identity compromise" if they found any. By April 13, 2021, the US Justice Department said owners had removed web shells from thousands of computers, yet hundreds persisted, so the FBI deleted them under court order.
ProxyLogon victims at least had a patch within days. A permanently vulnerable server never gets one. And state groups still target on premises mail: on November 11 we reported on Turla's Cereal malware reading government Exchange email.
What This Means for Your Inbox
An Exchange server is not just another box on the network: it holds every mailbox, every attachment and the company directory. Earlier this year an Exchange flaw, CVE-2026-96940, let one user read another's mail. On a permanently vulnerable server, the next bug of that kind simply never closes.
The risk also travels outward. You may use Gmail yourself, but your accountant or your hospital may still run Exchange 2016 in a closet. A compromised mail server can send messages from real accounts, inside real threads, which defeats the advice to check the sender address. Microsoft's November post notes that Exchange Online customers are already protected, so the exposure sits with organizations that host their own mail.
What Should Exchange Admins Do Now?
Admins should inventory every Exchange server, move to a supported platform, and isolate whatever cannot move yet. In order:
- Inventory. Run Microsoft's Exchange Server Health Checker across the organization, including management only and hybrid servers, which Microsoft says still need updates.
- Pick a path. Exchange 2019 CU14 or CU15 can upgrade in place to SE. Exchange 2016 cannot: it must reach CU23, then go through a side by side legacy migration to a new SE server. The upgrade guide also notes SE setup blocks coexistence with Exchange 2013.
- Budget for licensing. SE licensing matches 2019 but requires an active subscription: Software Assurance on server licenses and CALs, or qualifying cloud subscriptions such as Microsoft 365 E3 or E5. Moving mailboxes to Exchange Online is the other route.
- Isolate the stragglers. CISA and NSA's October 2025 Exchange hardening guidance tells anyone on an unsupported version to keep it off the public internet, put it in a dedicated network segment, and route outside mail through a separate, supported email security gateway, as Help Net Security summarized. Close OWA and ECP to the internet first.
- Hunt before you migrate. Credentials and Active Directory access stolen through an old server survive a mailbox migration. Following AA21-062A, look for unexpected aspx files under the IIS and Exchange auth directories, review ECP logs, and check for new mailbox export requests.
- Fix the scanner gap. Mark Exchange 2016 and 2019 as end of life in your vulnerability management tool so the absence of new CVE matches does not read as a clean bill of health.
What Should Employees and Email Recipients Do?
Employees should find out what their company runs and treat odd requests from partners on legacy Exchange with extra suspicion. If your work webmail address ends in /owa on a company domain rather than outlook.office.com, ask IT which version sits behind it; the CISA and NSA guidance is a useful document to forward.
- Verify payment changes, new bank details and document share links by phone, even when the message sits in a long, genuine thread.
- Do not reuse your work password anywhere; a dumped server exposes it.
What Comes Next?
Every Patch Tuesday from here produces a fresh list of Exchange SE fixes that attackers can diff against 2019 code, and Microsoft will not say which ones apply. Watch the monthly Exchange Team blog releases and the CISA Known Exploited Vulnerabilities list for Exchange entries. CISA's enrichment of the CVE-2026-118207 record listed exploitation as none at publication. Microsoft extended once after promising it would not; its Period 2 post rules out another. Plan as if that is final.