Microsoft has issued a revised set of September Exchange Server security updates, giving businesses a fresh reason to check the machines that still support their email environment. The October 2 release includes systems used for management, a detail that can be overlooked when most employees use cloud mailboxes.
In its Exchange Team announcement, Microsoft says the V2 release adds CVE-2026-96940. The company says it identified the vulnerability internally and was not aware of active exploitation. It recommends reviewing deployment guidance and applying the update at the earliest opportunity.
Exchange Online is already protected against the vulnerabilities covered by these updates, according to Microsoft. Organizations must still address Exchange servers and management-tools machines they operate. Updates for Exchange 2016 and 2019 require enrollment in the relevant Period 2 Extended Security Updates program; administrators should check the supported version and entitlement before deployment.
Cloud mail does not answer the inventory question
For a business owner, the practical starting point is a specific question to the person responsible for email: which machines remain in our environment, and who maintains each one? A statement that the company moved to the cloud is not the same as a current inventory.
The issue is organizational as much as technical. A server may be outside everyday view while still belonging to an important administrative process. If its owner changed during a migration or outsourcing arrangement, a new security announcement can expose a gap in responsibility rather than a gap in available software.
Ask for a short, dated record of the systems reviewed, their supported update path and the person accountable for completion. That provides a clearer basis for follow-up than an email saying the notice has been forwarded to IT.
Plan the work and verify the result
Microsoft’s announcement points administrators to its Health Checker and deployment guidance. It also lists known issues, so the release notes should be read as a whole rather than reduced to a download link.
A sensible change record should connect the update to the business functions that need checking afterward. For example, the team can identify who will confirm that ordinary messages and the organization’s relevant administrative workflows behave as expected. The exact test belongs to the company’s configuration, not a universal checklist copied from an unrelated installation.
For firms using a service provider, clarify whether the contract covers management-tools workstations as well as servers. Record which party supplies the evidence of completion and how an unsuccessful installation will be escalated. These questions turn an ambiguous shared responsibility into a task with a named owner.
Keep the risk statement precise
Microsoft’s statement that it was unaware of active exploitation is not a promise about future activity. It is also not evidence that a particular business has been compromised. Both exaggerated alarm and casual dismissal can distract from the immediate work of checking applicability and carrying out the vendor’s guidance.
The business implication is straightforward: email infrastructure needs an accurate inventory even after a cloud transition. A security update reaches its purpose only when the organization knows what it operates and can verify that the relevant work was completed.
For the wider security context, see our analysis of Microsoft’s latest Digital Defense Report.
Illustrative circuit board; not an affected Exchange system. Photo: Pixabay / Pexels.


