Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed Exchange endpoint over network
-
DeliverySend crafted overflow-triggering request
-
ExploitOverflow stack buffer in parser
-
ExecutionBypass memory mitigations
-
ImpactExecute arbitrary code on server
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The description specifies only a network-reachable stack-based buffer overflow with no stated configuration precondition, consistent with AV:N/PR:N/UI:N - i.e., remote unauthenticated exploitation against an Exchange Server reachable over the network. The key limiting factor is AC:H: successful exploitation depends on conditions outside the attacker's direct control (e.g., defeating stack protections, memory layout/timing, or reaching a specific vulnerable code path), which makes reliable exploitation non-trivial and non-automatable (SSVC Automatable=no). Exposure is further bounded to unpatched builds below the fixed versions: Exchange Server Subscription Edition RTM <15.02.2562.056, 2019 CU15 <15.02.1748.055, 2019 CU14 <15.02.1544.050, and 2016 CU23 <15.01.2507.077. Internet-facing Exchange deployments are at materially higher risk than internally segmented ones. |
| Impact | Signals are mixed and point to a serious-but-not-imminent threat. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N) confirms a remote, unauthenticated, no-user-interaction path with total CIA impact (C:H/I:H/A:H), which is why the base score reaches 8.1 (High). The limiting factor is AC:H - attack complexity is high, meaning exploitation is not trivially repeatable and likely depends on conditions or mitigation bypasses an attacker cannot fully control. CISA's SSVC framework corroborates a lower operational urgency: Exploitation=none (no observed exploitation) and Automatable=no (cannot be reliably mass-scanned/weaponized), even though Technical Impact=total aligns with the full RCE claim. No KEV listing and no POC are present in the data, so there is no public exploit identified at time of analysis. Net assessment: this is a genuinely high-impact pre-auth RCE in a high-value target (Exchange), so it should be prioritized for patching, but the AC:H rating plus SSVC 'none/no' indicate it is not currently a mass-exploited, automatable threat - treat it as high-priority patch management rather than an active-incident emergency. EPSS score was not provided in the input and therefore cannot be factored in; absence of EPSS is a data gap, not a signal of low risk. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends specially crafted network traffic to an internet-exposed Microsoft Exchange Server, triggering a stack-based buffer overflow (CWE-121) in a network-facing component and achieving arbitrary code execution in the Exchange process context. Because the CVSS vector is AV:N/PR:N/UI:N, no credentials or user interaction are needed, but AC:H means the attacker must satisfy non-trivial conditions or bypass memory protections for reliable exploitation. No public exploit identified at time of analysis, so any current attempt would require original exploit development. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Remote unauthenticated code execution in Microsoft Exchange Server is possible via a stack-based buffer overflow in affected builds of Exchange Server Subscription Edition RTM, Exchange Server 2019 CU14/CU15, and Exchange Server 2016 CU23, rated CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Attackers with network reachability to an unpatched Exchange deployment need no credentials and no user interaction, and the assessed impact is total (confidentiality, integrity, and availability all rated High). The high attack complexity component indicates that reliable exploitation depends on conditions outside the attacker's direct control, such as defeating stack protections or reaching a specific vulnerable code path, and CISA SSVC records Exploitation: none and Automatable: no; no public exploit identified at time of analysis, and Microsoft has released fixed builds.
RemediationAI
Primary remediation is to apply the Microsoft Exchange Server security update for this CVE, bringing systems to at least Exchange Server Subscription Edition RTM 15.02.2562.056, Exchange Server 2019 CU15 15.02.1748.055, Exchange Server 2019 CU14 15.02.1544.050, or Exchange Server 2016 CU23 15.01.2507.077; instructions and package links are in the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70571 and mirrored in NVD and ENISA EUVD EUVD-2026-100139. Because the SSVC assessment indicates exploitation is neither observed nor automatable, patching can follow a risk-prioritized schedule, but internet-facing servers should be treated as urgent. As a compensating control where immediate patching is not feasible, restrict external network access to Exchange endpoints (OWA, ECP, EWS, Autodiscover, ActiveSync, and SMTP) by placing them behind a VPN, an authenticating reverse proxy, or an IP allowlist, and block direct inbound reachability on port 443 and related service ports from the internet; the trade-off is loss of direct native mail and mobile client access, requiring users to connect through VPN or a proxied front end. Additional controls include segmenting Exchange from high-value internal networks and enabling crash telemetry on Exchange processes (for example, Windows Error Reporting or Exchange diagnostic logging) to detect attempted buffer-overflow exploitation, though monitoring alone does not prevent compromise and should not be treated as a substitute for the vendor fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 4 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-121 (Stack-based Buffer Overflow) describes a memory-safety defect in which data written to a fixed-size stack buffer exceeds its bounds, overwriting adjacent stack memory including saved frame pointers and return addresses. In Microsoft Exchange Server this class of bug resides in network-facing code paths within the Exchange service stack, allowing a remote, unauthenticated attacker (PR:N, UI:N, AV:N) to corrupt memory with attacker-influenced data and potentially redirect execution to attacker-controlled code, yielding the High confidentiality, integrity, and availability impact reflected in the CVSS vector. The AC:H rating reflects that exploitation is not deterministic or trivially automatable: modern compiler and OS mitigations such as stack cookies, ASLR, and DEP complicate control-flow hijacking, and the attacker must reach a specific vulnerable parsing path. SSVC corroborates this with Automatable: no while assigning Technical Impact: total, meaning that although exploitation is non-trivial, a successful compromise would grant full control of the Exchange process context. The affected code exists across multiple servicing branches (15.02.x for Subscription Edition and Exchange 2019, 15.01.x for Exchange 2016), so the fix is delivered across all supported cumulative updates.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable and unauthenticated with no user interaction (AV:N/PR:N/UI:N); AC:H because reliable overflow exploitation requires bypassing memory protections, yielding full code-execution impact (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Stack-based buffer overflow in Microsoft Exchange Server allows an unauthorized attacker to execute code over a network.
Executive ViewAI
Microsoft Exchange Server deployments are affected by a high-severity remote unauthenticated code execution vulnerability that could allow an attacker with network reachability to fully compromise email and calendaring services. Although no public exploit has been identified at time of analysis and reliable exploitation depends on conditions outside the attacker's direct control, a successful attack could result in unauthorized access to mailbox data, integrity loss, and disruption of a business-critical communications platform. Leadership should prioritize patching because unpatched Exchange servers represent a high-value entry point for organizational compromise.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
EUVD-2026-100139
GHSA-6m32-fvj6-jjf4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB