Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege Exchange credentials
  2. Delivery
    Reach network-facing Exchange service
  3. Exploit
    Send crafted request overflowing heap buffer
  4. Execution
    Corrupt heap memory structures
  5. Persist
    Execute arbitrary code in server context
  6. Impact
    Compromise mail server confidentiality/integrity/availability

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap 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

Exploitation requires the attacker to hold valid low-privilege authentication to the Exchange Server (CVSS PR:L), reachable over the network (AV:N), with no user interaction needed (UI:N) and low attack complexity (AC:L). The concrete prerequisite is an authenticated foothold - such as a compromised or attacker-owned mailbox/domain account able to reach an Exchange network service - after which the crafted input triggers the heap overflow. Limiting factors: the authentication requirement blocks purely anonymous internet attackers, exploitation targets the on-premises builds listed (Exchange 2016 CU23, 2019 CU14/CU15, Subscription Edition RTM), and the internal service endpoint must be network-reachable from the attacker's position.

Impact

The CVSS base score of 8.8 (High) reflects a network attack vector, low attack complexity, no user interaction, and only low privileges required, with high impact to all three security properties - a genuinely serious combination for an internet-adjacent mail server. However, PR:L means the attacker must already hold at least a low-privilege authenticated foothold (e.g., a valid mailbox account), which meaningfully raises the bar versus a pre-auth flaw. No EPSS score was provided, so probabilistic exploitation likelihood cannot be quantified, and no SSVC decision data was supplied. It is not in CISA KEV and no POC is referenced, so there is no evidence of active or automated exploitation yet; nonetheless, Exchange is a historically high-value, heavily-targeted target, so patching should be prioritized despite the authentication precondition. No data conflicts were observed between the CVSS vector and the description - both consistently indicate authenticated network code execution.

Exploit ScenarioDerived

An attacker who has obtained or been granted a low-privilege Exchange mailbox account sends a crafted request to a network-facing Exchange service, triggering the heap-based buffer overflow and executing code in the server's context. Because no user interaction is required and attack complexity is low, a single authenticated session is sufficient; no public POC is currently identified, so a working exploit would need to be developed.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 14, 2026

Remote code execution in Microsoft Exchange Server (2016 CU23, 2019 CU14/CU15, and Subscription Edition RTM) lets an authenticated attacker corrupt heap memory to run arbitrary code across the network. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) shows low-privilege network exploitation with full confidentiality, integrity, and availability impact, and Microsoft has released a patch. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

RemediationAI

Apply the Microsoft security update for CVE-2026-55005 as published in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55005 (Patch available per vendor advisory); install the corresponding fixed cumulative-update or security-update package for your specific build - Exchange 2016 CU23, Exchange 2019 CU14 or CU15, or Exchange Server Subscription Edition RTM. The advisory does not expose a single independently-confirmed fixed version string here, so pull the exact SU/CU build from MSRC for your servicing level before deployment. As compensating controls until patching, restrict which accounts can authenticate to Exchange and tighten mailbox account hygiene (since exploitation requires low-privilege authentication), place OWA/EWS behind a VPN or reverse proxy with pre-authentication to limit reachable attack surface, and enforce MFA to reduce the pool of usable low-privilege credentials - noting these controls reduce but do not eliminate risk for any attacker who already holds valid credentials, and proxy/VPN gating may disrupt legitimate mobile or federated access.

Affected VersionsENISA

Microsoft Exchange Server 2019 Cumulative Update 15 15.02.0.0 <15.02.1748.048
Microsoft Exchange Server 2016 Cumulative Update 23 15.01.0.0 <15.01.2507.071
Microsoft Exchange Server Subscription Edition RTM 15.02.0.0 <15.02.2562.045
Microsoft Exchange Server 2019 Cumulative Update 14 15.02.0.0 <15.02.1544.043

Affected Packages

euvd microsoft_exchange_server_2016_cumulative_update_23 fix: 15.01.2507.071
euvd microsoft_exchange_server_2019_cumulative_update_14 fix: 15.02.1544.043
euvd microsoft_exchange_server_2019_cumulative_update_15 fix: 15.02.1748.048
euvd microsoft_exchange_server_subscription_edition_rtm fix: 15.02.2562.045

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

The flaw is a CWE-122 heap-based buffer overflow, meaning a buffer allocated on the heap is written past its bounds, corrupting adjacent heap metadata or objects and enabling attacker-controlled memory to influence execution flow. It resides in Microsoft Exchange Server, the on-premises enterprise mail and calendaring platform that exposes numerous network-facing services (OWA, EWS, autodiscover, transport). The CPE data pins the affected code to Exchange Server 2016 Cumulative Update 23, Exchange Server 2019 Cumulative Update 14 and 15, and the newer Exchange Server Subscription Edition RTM, indicating the vulnerable component is shared across the current supported servicing baselines rather than a single legacy build.

Know when Microsoft Exchange Server 2016 Cumulative Update 23 gets its next vulnerability

  • 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

Vendor (microsoft) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 8.8 HIGH

Network-reachable service exploitable with a low-privilege authenticated account and no user interaction, yielding full code execution and thus high C/I/A on an unchanged scope.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Heap-based buffer overflow in Microsoft Exchange Server allows an authorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

Microsoft Exchange Server versions 2016 CU23, 2019 CU14/CU15, and Subscription Edition RTM contain a remote code execution vulnerability allowing authenticated users to execute arbitrary code on mail servers. This directly threatens email availability, data confidentiality, and business continuity for any organization relying on these versions.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.7%
Top 52% exploitable
Prevalence
High
widely deployed on-premises enterprise mail server across large organizations
Threat Intel
1
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
7 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.7%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

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 heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy