Skip to navigation

Threat reportVulnerabilityTL-2026-2864

Microsoft Reissues September 2026 Exchange Server Updates (V2) for CVE-2026-96940 Mailbox Authorization Flaw

highPATCHED

Microsoft released V2 of its September 2026 Exchange Server security updates after the original release (SU10, 8 September) did not include a fix for CVE-2026-96940, a weak authorization flaw (CVSS 8.8) that lets an authenticated attacker access other users' mailboxes within the same organization.

Key facts

IdentifiersTL-2026-2864, CVE-2026-96940
Also known asExchange September 2026 V2 Security Updates, Exchange SE SU10v2
SeverityHIGH
CVSS8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
EPSSCVE-2026-96940: 0.4% (40.6th percentile)
Affected productsMicrosoft Exchange Server Subscription Edition; Microsoft Exchange Server 2019; Microsoft Exchange Server 2016
Weaknesses (CWE)CWE-1390
ToolsExchange Server Health Checker (HealthChecker.ps1)
MITRE ATT&CK techniquesT1068 Exploitation for Privilege Escalation, T1078 Valid Accounts, T1087.003 Account Discovery: Email Account, T1114 Email Collection, T1114.002 Email Collection: Remote Email Collection
MotivationUNKNOWN
Target sectorsgovernment administration, finance, health, enterprise, technology
Target regionsGlobal
Detection rules9 (1 shown free)
Sources10 cited sources

Detection coverage

As of 2026-10-10, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2864 across Splunk SPL, Microsoft KQL and Sigma, covering 21 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Exchange OWA Cross-Mailbox Access by Non-Owner Account (CVE-2026-96940) — Exploitation

CVE-2026-96940 is a weak-authorization flaw (CWE-1390) that lets an authenticated low-privileged user reach other users' mailboxes in the same on-premises Exchange organization. No exploit mechanics are public, so this is a behavioural detection: IIS requests to /owa/<smtp>/ where the SMTP alias in the URL differs from the authenticated account alias. It also surfaces legitimate shared-mailbox/delegate access, so the output must be reviewed against delegation records. Mailboxes touched and source IPs are returned for triage.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1078, T1068, T1114.002
  • Data sources: IIS W3C logs (Exchange Front End, ms:iis:auto), W3CIISLog, Exchange OWA
  • Severity: high
  • Confidence: medium

Splunk SPL

```Cross-mailbox OWA access: authenticated alias differs from the mailbox SMTP in /owa/<smtp>/```
index=iis sourcetype="ms:iis:auto" earliest=-24h (cs_uri_stem="/owa/*@*" OR cs_uri_stem="/OWA/*@*") sc_status IN (200,302) cs_username!="-"
| rex field=cs_uri_stem "(?i)^/owa/(?<target_mailbox>[^/]+@[^/]+)/"
| rex field=cs_username "(?<caller_alias>[A-Za-z0-9._-]+)(?:@[^@]*)?$"
| eval target_alias=lower(mvindex(split(target_mailbox,"@"),0)), caller_alias=lower(caller_alias)
| where isnotnull(target_mailbox) AND caller_alias!=target_alias
| stats count AS requests dc(target_mailbox) AS mailboxes_touched values(target_mailbox) AS target_mailboxes values(c_ip) AS src_ips min(_time) AS first_seen max(_time) AS last_seen BY host cs_username
| convert ctime(first_seen) ctime(last_seen)
| sort - mailboxes_touched

Microsoft KQL

// Cross-mailbox OWA access: authenticated alias differs from the mailbox SMTP in /owa/<smtp>/
W3CIISLog
| where TimeGenerated > ago(24h)
| where csUriStem startswith '/owa/' and csUriStem contains '@'
| where csUserName != '-' and toint(scStatus) in (200, 302)
| extend TargetMailbox = tolower(extract(@'(?i)^/owa/([^/]+@[^/]+)/', 1, csUriStem))
| where isnotempty(TargetMailbox)
| extend CallerAlias = tolower(extract(@'([A-Za-z0-9._-]+)(?:@[^@]*)?$', 1, csUserName)), TargetAlias = tostring(split(TargetMailbox, '@')[0])
| where isnotempty(CallerAlias) and CallerAlias != TargetAlias
| summarize Requests = count(), MailboxesTouched = dcount(TargetMailbox), TargetMailboxes = make_set(TargetMailbox, 25), SrcIPs = make_set(cIP, 10), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by Computer, csUserName
| order by MailboxesTouched desc

Sigma

title: Exchange OWA Request Targeting Another Mailbox Path
id: 7d3b9c52-1a4e-4f08-b6c1-3e2a9d5f7001
status: experimental
description: Detects successful OWA requests whose URL carries an explicit mailbox SMTP (/owa/user@domain/). Under CVE-2026-96940 an authenticated low-privileged user could reach other users' mailboxes. Sigma cannot compare the URL mailbox to the authenticated user, so correlate cs-username against the URL mailbox in the SIEM; shared and delegated mailboxes are expected benign matches.
references:
  - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96940
  - https://techcommunity.microsoft.com/blog/exchange/released-september-2026-v2-exchange-server-security-updates/4561718
author: Threadlinqs Team
date: 2026/10/03
tags:
  - attack.initial-access
  - attack.t1078
  - attack.privilege-escalation
  - attack.t1068
  - attack.collection
  - attack.t1114.002
  - cve.2026-96940
logsource:
  category: webserver
detection:
  selection_path:
    cs-uri-stem|re: '(?i)^/owa/[^/]+@[^/]+/'
  selection_status:
    sc-status:
      - 200
      - 302
  filter_anonymous:
    cs-username: '-'
  condition: selection_path and selection_status and not filter_anonymous
falsepositives:
  - Users opening shared mailboxes or mailboxes they hold Full Access / delegate rights to
  - Help-desk or executive-assistant access to delegated mailboxes
level: medium

Known false positives:

  • Shared mailboxes and delegated/Full Access mailbox access
  • Executive assistants and help-desk staff acting on delegated mailboxes

Tuning notes: Join or exclude against the Get-MailboxPermission / Get-MailboxFolderPermission export of legitimate delegations. The alias comparison assumes alias equals the sAMAccountName local part; adjust it if your naming differs. The SPL field names (cs_username, cs_uri_stem, c_ip) follow the Splunk Add-on for Microsoft IIS, so change them to match your extraction. The research gives no exploit signature, so treat hits as leads rather than confirmed exploitation.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Exchange Servers Exposed to CVE-2026-96940 (Unpatched Original September 2026 Build) — Exploitation Exposure · unlock with TL Creds
  • Exchange Mailbox Forwarding or Redirect Rule Created via PowerShell — Post-Exploitation · unlock with TL Creds
  • Exchange Directory and Mailbox Enumeration Burst (FindPeople / Autodiscover / OAB) — Discovery · unlock with TL Creds
  • Exchange Client-Access Logon Failures Followed by Success from One Source (Valid Account Abuse) — Initial Access · unlock with TL Creds
  • Exchange Mailbox Export or Search-Mailbox Copy Staging via PowerShell — Post-Exploitation Collection · unlock with TL Creds
  • Scripted or Non-Standard Client Accessing Exchange EWS/OWA/MAPI/ActiveSync — Collection Tooling · unlock with TL Creds
  • Exchange Mailbox Permission or ApplicationImpersonation Grant via PowerShell — Post-Exploitation · unlock with TL Creds
  • Bulk EWS Mailbox Collection by a Single Account (Remote Email Collection) — Collection at Scale · unlock with TL Creds

Indicators of compromise

As of 2026-10-10, Threadlinqs Intelligence tracks 21 indicators of compromise for TL-2026-2864.

Sample indicators (3 of 21)

  • File hash: D2B8BB82E1B3F7A92A16B09C73B52CDB4FD41A99A766BC98BCF14A1D09B1509C
  • File hash: 88CAFCA051C8DC507F6042ECCCE3BDA34D8549C3EF497055BE560460B1250166
  • File hash: A57C3F87051FF6D9810475C37AA3F183C1C41A633E986C1747DA7758A1619F1B

Defanged, TLP:CLEAR. Full set of 21 indicators: unlock with TL Creds.

21 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Microsoft found the flaw internally and reported no active exploitation.

CVE-2026-96940 is a weak-authorization vulnerability (CWE-1390) in on-premises Microsoft Exchange Server. The CVE record describes it as allowing an authenticated attacker to elevate privileges over a network; Microsoft's Exchange Team and press coverage describe the practical impact as an authenticated attacker accessing other users' mailboxes in the same organization, exposing email messages and attachments. The scoring is CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8, High). No user interaction is required, and access does not cross tenant boundaries. Exchange Online customers are already protected.

Affected products are Exchange Server Subscription Edition (SE) RTM, Exchange Server 2019 CU14 and CU15, and Exchange Server 2016 CU23. Per CVE tracker data, vulnerable build ranges are 15.1.x below 15.1.2507.75 (2016 CU23), 15.2.x below 15.2.1544.48 (2019 CU14), 15.2.x below 15.2.1748.53 (2019 CU15) and 15.2.x below 15.2.2562.53 (SE RTM).

The original September 2026 Exchange security updates were released on 8 September 2026 (SE SU10 KB5121608; 2019 CU15 KB5121609; 2019 CU14 KB5121610; 2016 CU23 KB5121611) and addressed nine other CVEs, but not CVE-2026-96940. The CVE was reserved on 23 September 2026. The SE SU10v2 package (KB5129955) began appearing through Windows Update/WSUS on 1 October 2026 before any documentation existed, and Microsoft announced the 'September 2026 V2 Exchange Server Security Updates' on the Exchange Team Blog on 2 October 2026. The only difference between the original release and V2 is the addition of CVE-2026-96940. Microsoft said it published the V2 updates ahead of its intended schedule so attackers would not discover and exploit the flaw first.

Microsoft found the vulnerability internally and was not aware of active exploitation. The CVE is not in the CISA KEV catalog (version 2026.10.02), and no public proof-of-concept was detected by CVE trackers. Administrators who installed the earlier September release should install the V2 packages rather than assume they are protected. Updates are applied to every Exchange server and Exchange Management Tools workstation, including management-only systems in hybrid deployments. Exchange 2016 and 2019 updates are available only to organizations enrolled in the Extended Security Update (ESU) Period 2 program (May-October 2026), with no further extensions planned. Cyber Security News notes a separate earlier Exchange flaw, CVE-2026-62911 (authentication relay), as related context.

MITRE ATT&CK techniques by tactic:

Privilege Escalation

T1068 Exploitation for Privilege Escalation

Initial Access

T1078 Valid Accounts

Discovery

T1087.003 Account Discovery: Email Account

Collection

T1114 Email Collection; T1114.002 Email Collection: Remote Email Collection

Remediation

Patches

  • Exchange SE RTM: KB5129955 (SU10v2)
  • Exchange 2019 CU15, 2019 CU14, 2016 CU23: V2 security updates (ESU Period 2 enrollees), superseding KB5121609, KB5121610, KB5121611

Immediate actions

  • Install the September 2026 V2 Exchange security update on every on-premises Exchange server, even if the original September update (SU10, 8 Sep 2026) is already installed
  • Also update Exchange Management Tools workstations and management-only servers in hybrid deployments
  • Restart servers after installation and confirm Exchange services function properly

Workarounds

  • None documented in sources; Exchange Online customers are already protected

Longer-term hardening

  • Run the Exchange Server Health Checker script to identify missing updates
  • Identify installed version and cumulative update level (Get-Command Exsetup.exe) before and after patching
  • Plan migration off Exchange 2016/2019 or to Exchange SE; their updates are available only through ESU Period 2 (May-October 2026) with no further extensions planned

Affected and fixed versions

  • Microsoft — Exchange Server Subscription Edition
    Vulnerable versions: RTM (builds below 15.2.2562.53, including SU10 15.2.2562.49)
    Fixed in: SU10v2 (KB5129955)
  • Microsoft — Exchange Server 2019
    Vulnerable versions: CU15 (below 15.2.1748.53); CU14 (below 15.2.1544.48)
    Fixed in: September 2026 V2 security update (ESU Period 2)
  • Microsoft — Exchange Server 2016
    Vulnerable versions: CU23 (below 15.1.2507.75)
    Fixed in: September 2026 V2 security update (ESU Period 2)

Timeline

Last updated · 4 updates · revalidated 4× · latest source

  • Prior Exchange SE security update KB5121573 released; later superseded by the V2 package KB5129955.
  • Microsoft releases the original September 2026 Exchange security updates (SE SU10 KB5121608; 2019 CU15 KB5121609; 2019 CU14 KB5121610; 2016 CU23 KB5121611), which do not include a fix for CVE-2026-96940.
  • CVE-2026-96940 is reserved; Microsoft's own teams had identified the weak-authorization flaw internally.
  • Microsoft deploys a service-side fix for CVE-2026-96940 to Exchange Online in late September 2026, about a week before the on-premises V2 release (date approximate).
  • KB5129955 (Exchange SE RTM SU10v2) begins appearing via Windows Update/WSUS before any documentation is published; administrators initially advise caution.
  • Microsoft rates CVE-2026-96940 'Exploitation More Likely'; no in-the-wild exploitation is reported.
  • CVE-2026-96940 is published with CVSS 3.1 base score 8.8 and CWE-1390; MSRC advisory links the Security Update Guide entry.
  • Exchange Team Blog publishes 'Released: September 2026 V2 Exchange Server Security Updates'; the only change from the original release is the addition of CVE-2026-96940.
  • CISA Vulnrichment records SSVC for CVE-2026-96940: Exploitation None, Automatable No, Technical Impact Total.
  • Cyber Security News, Cryptika and Neowin report the V2 reissue; CVE record updated; flaw not in CISA KEV and no known exploitation.
  • GovCERT.HK publishes Security Alert A26-10-06 on the Exchange vulnerability and urges users to follow vendor recommendations.
  • The Hacker News reports the flaw lets authenticated attackers read other users' mailboxes and credits Jan Mitchell of Microsoft with the discovery.
  • NVD record last modified; status remains Undergoing Analysis, with no confirmed in-the-wild exploitation reported in the reviewed sources.

Update history

Sources cited

Other reports on CVE-2026-96940

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 10 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats