Skip to content

Security Independently confirmed3 publishers 2 min read Published Updated

Out-of-band Exchange Server patch closes a flaw that exposes colleagues' mail to signed-in attackers

Microsoft issued an out-of-band Exchange Server fix for CVE-2026-96940, a bug letting signed-in attackers read colleagues' mail and attachments. The company expects the flaw to be consistently exploitable, so on-premises admins have good reason to install it ahead of the next maintenance window.

The Watch · Security desk

Send a correction

Illustration accompanying Out-of-band Exchange Server patch closes a flaw that exposes colleagues' mail to signed-in attackers
Generated illustration

What happened

  • Microsoft says the flaw does not allow access across tenant boundaries, so exposure stays inside a single organization.
  • Microsoft found the bug internally and says it is not aware of any active exploitation.
  • A related service-side fix reached Exchange Online late last week, at first without a KB article explaining what it changed.
  • Microsoft later said the update had gone out ahead of its intended schedule, but did not say why.
  • Packages cover Exchange Server Subscription RTM, Exchange Server 2019 CU14 and CU15, and Exchange Server 2016 CU23.

Why it matters

  • Who's exposed exposure On any unpatched server, one compromised or malicious account inside the organization is enough to open other users' mail and attachments.
  • Who has to decide decision A vendor forecast of consistent exploitation, in a bug class attackers have used before, argues for taking the out-of-band patch now instead of holding it for the next scheduled window.
  • What it limits constraint Servers on cumulative updates outside the four covered builds have to reach a covered build before this fix can go on, which lengthens the path to being patched.
  • What it costs cost The change window grows to include every admin workstation running the Exchange Management Tools, beyond the mail servers themselves.

Exploitation requires one working login. The attacker has to be authenticated and inside the same organization as the target mailboxes [2]. Anyone holding a single valid account on an unpatched server meets that condition. An outsider with no credentials does not [11]. The flaw is rated high-severity [1].

Microsoft also points to history. It notes that this type of vulnerability has been exploited in the past, and it advises admins to update sooner rather than later [5][6]. No exploitation of this CVE is known, so there is no actor or campaign to tie it to yet [12]. The Exchange Server Team recommended that customers review the deployment guidance and install the September 2026 v2 update as soon as they can [8].

Exchange Online tenants got their fix on Microsoft's side of the service [7]. Their confusion was over what had changed, and the team's account of the rollout covers only its timing [13]. On-premises admins have to install the security update themselves [6].

The release has packages for four builds [14]. A server on any other cumulative update has nothing to install from it [15]. The install list also goes beyond the mail servers. "Our recommendation is to install SUs on all Exchange Servers and all servers and workstations running the Exchange Management Tools to ensure compatibility between management tools clients and servers," the team said [9].

What to watch

  • Any Microsoft revision to the 'not aware of active exploitation' status for CVE-2026-96940.
  • A public proof-of-concept or patch-diff writeup for CVE-2026-96940.
  • An explanation from Microsoft of why the update was published ahead of its intended schedule.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence74
Adoption
Not scored
Hype gap0
Incentives
Not scored
Confidence70

Perspective Coverage

3 publishers
Builder
Builder 15%
Operator
Operator 80%
Investor
Investor 5%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Microsoft pushed out an out-of-band security update for Exchange Server that fixes a high-severity vulnerability, CVE-2026-96940.

    Reported SupportedView cited source
  2. [2]

    CVE-2026-96940 may allow authenticated attackers to read emails and attachments of other users in the same organization.

    Reported SupportedView cited source
  3. [3]

    Microsoft says the flaw "does not allow access across tenant boundaries."

    Reported SupportedView cited source
  4. [4]

    CVE-2026-96940 was discovered internally, and the Exchange Server Team said they "are not aware of active exploitation."

    Reported SupportedView cited source
  5. [5]

    Microsoft thinks the flaw could be consistently exploited and notes that this type of vulnerability has been exploited in the past.

    Reported SupportedView cited source
  6. [6]

    Microsoft advises Exchange Server admins to update sooner rather than later.

    Reported SupportedView cited source
  7. [7]

    Microsoft deployed a related service-side fix to Exchange Online late last week, taking customers by surprise because the security updates were not immediately accompanied by a KB article explaining their content.

    Reported SupportedView cited source
  8. [8]

    "We recommend that customers review the deployment guidance and apply the [September 2026 v2] update at the earliest opportunity,"

    Reported Supported Source: Exchange Server Team, as quoted by Help Net SecurityView cited source
  9. [9]

    "Our recommendation is to install SUs on all Exchange Servers and all servers and workstations running the Exchange Management Tools to ensure compatibility between management tools clients and servers."

    Reported Supported Source: Exchange Server Team, as quoted by Help Net SecurityView cited source
  10. [10]

    The security update is available for on-prem servers running Exchange Server Subscription RTM, Exchange Server 2019 cumulative updates 14 and 15, and Exchange Server 2016 cumulative update 23.

    Reported SupportedView cited source
  11. [11]

    The precondition for exploitation is one valid account inside the target organization; an outside attacker with no credentials, or one in another tenant, does not meet it.

    Derived Supported
  12. [12]

    With no known exploitation reported by Microsoft, no threat actor or campaign is tied to CVE-2026-96940 yet.

    Derived Supported
  13. [13]

    Microsoft acknowledged the misstep; the Exchange Server Team said the release sequence was unusual because the update was published ahead of its intended schedule, and did not explain why that happened.

    Reported SupportedView cited source
  14. [14]

    The update covers four on-premises Exchange Server builds.

    Derived Supported
  15. [15]

    Servers on Exchange builds other than the four listed have no package in this release.

    Derived Supported

Sources

3 independent publishers whose own reporting we read for this story.

  1. helpnetsecurity.com

    1 article · October 5, 2026

    Out-of-band Exchange Server update fixes high-severity mailbox access bug (CVE-2026-96940)
  2. securityaffairs.com

    1 article · October 6, 2026

    CVE-2026-96940: Microsoft Fixes Exchange Server Flaw For Which Exploitation Is More Likely
  3. thehackernews.com

    1 article · October 5, 2026

    Microsoft Exchange Flaw Lets Authenticated Attackers Read Other Users' Mailboxes

Topics and entities

Topics