Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-96940: Authenticated Privilege Escalation in Microsoft Exchange Server

Published Oct 2, 2026 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS8.8High · v3.1
EPSS2.7%86th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-96940CWE-1390 · Weak Authentication

CVE-2026-96940 is a weak-authorization vulnerability in Microsoft Exchange Server that allows an authenticated attacker to elevate privileges over a network. Inadequate mailbox authorization checks can permit access to other users' email messages and attachments within the same Exchange organization, beyond the permissions assigned to the attacker's account. Affected on-premises releases include Exchange Server 2016 CU23, Exchange Server 2019 CU14 and CU15, and Exchange Server Subscription Edition RTM. The vulnerability has a CVSS v3.1 base score of 8.8. The precise vulnerable function, API endpoint, and triggering request sequence have not been publicly disclosed.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises mailbox confidentiality by exposing other users' emails and attachments within the same organization. Accessible information may include confidential correspondence, financial records, contracts, and authentication-related messages. Stolen information could facilitate data theft, targeted phishing, impersonation, and business email compromise. The vulnerability does not permit cross-tenant access and does not directly grant Windows administrator or SYSTEM privileges. Mailbox modification, deletion, and code execution are not established outcomes of this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific temporary workaround is specified. Until patching is complete, restrict network access to affected Exchange services, enforce strong authentication and multifactor authentication, review mailbox permissions, and minimize excessive RBAC privileges. These measures reduce exposure but do not correct the authorization flaw or prevent exploitation through an already authenticated account. Correlate authentication and mailbox-access logs to investigate unexpected cross-mailbox reads, authenticated-identity versus target-mailbox mismatches, and rapid access across multiple mailboxes, while accounting for legitimate delegation and service-account activity.

Remediation

Patch, then assume compromise.

Install the latest applicable Microsoft Exchange Server V2 security update or a superseding update containing the fix. The identified updates and minimum fixed builds are: Exchange Server 2016 CU23 SU25V2, KB5129958, build 15.01.2507.075; Exchange Server 2019 CU14 SU14V2, KB5129957, build 15.02.1544.048; Exchange Server 2019 CU15 SU11V2, KB5129956, build 15.02.1748.053; and Exchange Server Subscription Edition RTM SU10V2, KB5129955, build 15.02.2562.053. Verify installed builds and run Exchange Server Health Checker after deployment. Validate mail flow, client access, calendars, and applicable hybrid functionality. Exchange Server 2016 and 2019 require appropriate Extended Security Update entitlement for the relevant updates; organizations without update coverage should migrate to a supported, patched Exchange Server Subscription Edition deployment. Exchange Online has received a service-side fix and requires no customer action.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
cve-2026-62911-pocThis standalone repository contains four files: poc.py, README.md, requirements.txt, and an MIT LICENSE. The listed file sizes total 45,559 bytes; the archive size and analyzed Git reference were not provided, so size_bytes is an unknown-value placeholder. Python is the sole source-file language, with an embedded C# ASPX payload. Dependencies are impacket>=0.11.0 and pysocks; neither makes this an exploit-framework module. The README advertises a scanner and an exploitation chain for CVE-2026-62911: coerce an Exchange machine account through PetitPotam/MS-EFSR, relay its NTLM authentication to another Exchange server's MRSProxy HTTPS endpoint, invoke IMailbox_Config6 with a web-accessible ASPX destination, and invoke IMailbox_Connect to trigger a file write. The embedded webshell is concrete and executes request-supplied commands. The visible orchestration starts a relay listener, calls the coercion function, waits up to 120 seconds, and attempts webshell verification after reported success. It warns about a negative pre-check but continues after a short delay rather than enforcing a safety gate. Scanner capabilities are advertised as HTTP.sys/MRSProxy detection, Exchange version discovery, NTLM target-information extraction, file-based batch scanning, and JSON output. CVE-2026-96940 is represented by a version/patch database describing organization-wide mailbox access; no mailbox exploitation is visible. Version matching and an HTTP 401/Microsoft-HTTPAPI response alone would not prove missing EPA or exploitable relay behavior. The central portion of poc.py is explicitly truncated, omitting the scanner, RPC coercion, NTLM relay, WCF serialization, file-write implementation, and verification logic. Therefore this is identifiable as an exploit attempt with a hardcoded operational payload, not merely a detector, but its functionality, claimed zero-credential access, SYSTEM execution, CVE assignments, and patch thresholds cannot be independently validated from the supplied material. There is insufficient evidence to label it fake. One visible correctness issue is that the NTLM AV_PAIR labels swap computer/domain meanings for IDs 1/2 and 3/4, potentially mislabeling reconnaissance output. No fixed attacker infrastructure, exfiltration destination, or registry modification is visible; network hosts are supplied at runtime.c5z54 · Disclosed Nov 2, 2026 · python · csharp · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationExchange Serverapplication
Microsoft CorporationExchange Server 2016application
Microsoft CorporationExchange Server 2019application
Microsoft CorporationExchange Server Seapplication
Microsoft CorporationExchange Server Subscription Editionapplication
FAQ

Frequently asked questions

Is CVE-2026-96940 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-96940 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-96940?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-96940, the earliest disclosed Nov 2, 2026.
Is there a patch for CVE-2026-96940?
Install the latest applicable Microsoft Exchange Server V2 security update or a superseding update containing the fix. The identified updates and minimum fixed builds are: Exchange Server 2016 CU23 SU25V2, KB5129958, build 15.01.2507.075; Exchange Server 2019 CU14 SU14V2, KB5129957, build 15.02.1544.048; Exchange Server 2019 CU15 SU11V2, KB5129956, build 15.02.1748.053; and Exchange Server Subscription Edition RTM SU10V2, KB5129955, build 15.02.2562.053.
What products are affected by CVE-2026-96940?
Microsoft Corporation Exchange Server, Microsoft Corporation Exchange Server 2016, Microsoft Corporation Exchange Server 2019, Microsoft Corporation Exchange Server Subscription Edition, and Microsoft Corporation Exchange Server Se.
How severe is CVE-2026-96940?
CVE-2026-96940 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 2.7% (86th percentile) as of Nov 4, 2026.
Activity feed

Recent activity

121 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cysecurity newsNews · Oct 9, 2026Microsoft Exchange Vulnerability Could Leak Confidential Organizational Info - CySecurity News - Latest Information Security and Hacking IncidentsAn authorization-control vulnerability in Microsoft Exchange Server allows authenticated attackers to elevate their Exchange permissions over a network and access other users’ emails and attachments. Rated CVSS 8.8, it could expose confidential communications and facilitate fraud or business email compromise. It does not enable cross-tenant access or directly grant administrator or SYSTEM privileges on the underlying Windows server. Microsoft released an emergency fix on October 2 and reported no evidence of active exploitation at the time of the report.Read more ↗uganda certNews · Oct 7, 2026Microsoft Exchange Server Elevation of Privilege Flaw Is October's Only Patch Tuesday Fix (CVE-2026-96940) | Uganda National Computer Emergency Response Team-National CertAn elevation-of-privilege vulnerability affecting all supported on-premises versions of Microsoft Exchange Server, rated CVSS 8.8. The report describes its potential use as a follow-on step after an initial compromise to gain control of the mail system. Microsoft assesses exploitation as more likely, but the report states that no public exploitation has been confirmed.Read more ↗tenable nessus pluginsNews · Oct 7, 2026Microsoft Exchange Server Elevation of Privilege (October 2026) | Tenable®A high-severity elevation-of-privilege vulnerability in Microsoft Exchange Server 2016, 2019, and Subscription Edition. Weak authorization allows an authenticated attacker with low privileges to elevate privileges over a network without user interaction. The listed CVSS v3 score is 8.8. Microsoft released security updates on October 2, 2026. The Nessus plugin detects potentially affected installations using self-reported application versions rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Oct 7, 2026Security Updates for Microsoft Exchange Server (October 2026 OOB) | Tenable®A high-severity elevation-of-privilege vulnerability in Microsoft Exchange Server caused by weak authorization. An authenticated attacker with low privileges can exploit it remotely without user interaction, potentially compromising confidentiality, integrity, and availability. The listed CVSS v3 base score is 8.8. Nessus identifies potentially affected installations using self-reported application versions rather than testing exploitation.Read more ↗
+24 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity90Community discussion across Reddit, Mastodon, and other social sources.