Microsoft’s November 10 Patch Tuesday included a critical Windows Search flaw, CVE-2026-116928, scored 9.8. On an Exchange server, Microsoft says, an outsider can send an email with a crafted attachment and the server indexes it on its own. Nobody has to open the message.
Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.
Microsoft marks it as not exploited and “Exploitation Less Likely”. That gives mail admins a window, and the fix ships in the monthly Windows update.
The Windows Search flaw CVE-2026-116928 reaches Exchange through attachment indexing. No exploitation is reported. Install the November Windows Server update on every Exchange box, including Exchange 2016 and 2019.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
A Windows Search bug can run code on an Exchange server from one email
CVE-2026-116928 is an out-of-bounds write in the Windows Search component. Microsoft’s advisory says an unauthenticated attacker could exploit the Windows Search component used by Exchange Server by sending an email that has a specially crafted attachment. Exchange processes the attachment for indexing, and code would run with the permissions of the processing service.
- Windows Server 2025: KB5131080 (build 26100.33822).
- Windows Server 2022: KB5131090 (build 20348.5870).
- Windows Server 2019: KB5131085 (build 17763.9487).
- Windows Server 2016: KB5131291 (build 14393.9688).
- Exchange SE: a separate update, SU12 (KB5133453), fixes nine Exchange bugs from the same day, per Messageware’s count. Install both packages; the order doesn’t matter.
Exchange servers that index mail, and Exchange 2016 and 2019 in particular
Exchange 2016 and 2019 no longer get security updates. Microsoft’s Exchange team says those versions are no longer tested for vulnerabilities and should be considered permanently vulnerable. The Windows update is the one fix that still reaches them, because the flaw is in Windows and not in Exchange.
Nothing here is under attack yet, and CVE-2026-116928 is not in CISA’s exploited catalog as of the November 17 update. A mail server is reachable by anyone who can send it an email, so attackers who compare the patched and unpatched files have an easy target if they get a working exploit. The window is short and the patch is already out.
Install November’s Windows update on every Exchange server
- List every server with the Exchange role, plus any Exchange Management Tools workstation, and note each one’s Windows version.
- Install the November cumulative update for that Windows version on every one of them, then reboot. Do this first on the servers that take mail from the internet.
- On Exchange SE servers, also install SU12 (KB5133453). Exchange Online is already protected, according to Microsoft.
- If you still run Exchange 2016 or 2019, plan the move to Exchange SE or Exchange Online. The Windows patch closes this bug and nothing else.
- If your Exchange servers turned unstable after October’s Windows updates, Microsoft says the November Windows update is the fix for that too.
Forward this
For whoever runs our email servers: Microsoft’s November Windows update fixes a critical bug that can let a stranger run code on an Exchange server just by emailing it a booby-trapped attachment. Nobody is using it yet. If we host Exchange ourselves, can we get the November Windows update on those servers this week? If we are on Microsoft 365 (Exchange Online), Microsoft says it is already covered.
Details
- CVE-2026-116928: out-of-bounds write in the Windows Search component, remote code execution. CVSS 3.1: 9.8. Published November 10, 2026. NVD status: awaiting analysis.
- Microsoft’s rating: Critical, “Exploitation Less Likely”, customer action required. Exchange route described in the advisory FAQ: crafted attachment, automatic indexing.
- Exchange: SE RTM SU12 is KB5133453 (build 15.02.2562.057), released November 10. Exchange 2016 and 2019 get no update.
- Exploitation: none reported; not in CISA’s KEV catalog as of its November 17 update. Status: THEORETICAL.
Hunt / verify
- Run Microsoft’s Exchange Server Health Checker to see each server’s build and whether it has the latest update.
- Compare each Exchange server’s Windows build with the numbers above. A server on an older build still has the bug.
- Look in the Windows Application and System logs for Windows Search indexer crashes (SearchIndexer or SearchProtocolHost) since November 10. Repeated crashes on a mail server are worth a closer look.
Source: Microsoft advisory; Exchange team post
Sources
- Microsoft MSRC: CVE-2026-116928 Windows Search Remote Code Execution
- OpenAdvisories: MSRC copy of the CVE-2026-116928 advisory (Exchange FAQ, exploitability, KB list)
- NVD: CVE-2026-116928
- Microsoft: KB5131080, Windows Server 2025
- Microsoft: KB5131090, Windows Server 2022
- Microsoft: KB5131085, Windows Server 2019
- Microsoft: KB5131291, Windows Server 2016
- Exchange Team: Released: November 2026 Exchange Server Security Updates
- Microsoft: KB5133453, Exchange Server SE SU12
- Messageware: November 2026 Exchange Server security updates
- Invitty: Exchange CVE-2026-116928 patch guide
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.