No More Patches, No More Testing: Microsoft Now Calls Exchange 2016 and 2019 ‘Permanently Vulnerable.’ The Fact Sheet and a Move-Off Checklist
November’s Exchange security fixes shipped for Exchange Server Subscription Edition only, and Microsoft’s release notes tell anyone still on Exchange 2016 or 2019 to treat those servers as permanently vulnerable. Here are the key dates, what changed this month, and a checklist for getting off the old versions.
For organizations still running Exchange Server 2016 or 2019 on premises, November marked a hard stop. Microsoft’s documentation for this month’s Exchange security update carries a blunt message: those versions are no longer tested for vulnerabilities, they receive no updates, and anyone using them should consider them “permanently vulnerable” and upgrade immediately. The Register spotted the warning in the release notes; the essentials are laid out below.
Fact sheet
- Products affected: Exchange Server 2016 and Exchange Server 2019, on premises.
- Still supported: Exchange Server Subscription Edition (SE), plus Microsoft’s online service.
- End of support: October 14, 2025.
- Paid lifeline: An Extended Security Updates (ESU) program, announced in July 2025, was meant to end on April 14, 2026, with Microsoft saying at the time it would not be extended. It was, by six more months of paid updates.
- Final updates for 2016/2019: October 13, 2026.
- November 2026 update: Nine vulnerabilities fixed in Exchange Server SE, including a critical remote code execution flaw, CVE-2026-118207. Microsoft is not testing older versions against these flaws.
- Microsoft’s guidance: Treat 2016 and 2019 as permanently vulnerable and upgrade the organization immediately.
Why this matters more than a typical end-of-life notice
On-premises Exchange sits on the internet by design, holds every mailbox in the company and has been a favorite target for years. Without testing, nobody will tell you whether the latest critical flaw in Exchange SE also exists in 2016 or 2019. Each future Patch Tuesday widens the gap between what attackers can learn from published fixes and what protects an unpatched server.
Move-off checklist
- Confirm what you run. Check the version and build of every Exchange server, including hybrid servers kept only for management and any forgotten test or recovery boxes.
- Pick a destination. The supported routes are Exchange Server SE on premises or a move to hosted email. The choice depends on compliance needs, budget, public folder use and how many line-of-business apps relay through Exchange.
- Set a date and own it. Give the migration an owner and a deadline measured in weeks, not quarters.
- Reduce exposure while you wait. Limit what the old server exposes to the internet, put web access and remote PowerShell behind a VPN or a filtering reverse proxy where possible, and keep the Windows Server underneath fully patched.
- Raise monitoring. Watch for new web shells, unusual processes spawned by Exchange services, new mailbox forwarding rules and unexpected admin accounts. Make sure alerts reach a person at any hour.
- Back up and test restores. Confirm you can recover mailboxes and the server if an attack or a failed migration step goes wrong.
- Inventory dependencies. List scanners, copiers, applications and scripts that send mail through Exchange so they do not break on cutover day.
- Decommission properly. After the move, remove the old servers cleanly rather than leaving them powered on and forgotten.
What this means for your company
If Exchange 2016 or 2019 still handles your email, you are running a critical, internet-facing system that its maker has stopped fixing or even testing. That is a business risk, not just an IT one: a compromise can expose every message, contract and invoice in the company and give attackers a trusted platform to phish your customers. The fix is a planned migration with interim protections, and the time to start is now. If you have already moved, double-check that no old server is still quietly running in a closet or a virtual host.
Weighing Exchange SE against a move to hosted email, or need a hand keeping an old server safe until cutover? Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.
