Skip to main content

Microsoft Exchange Server CVE-2026-55009

| EUVDEUVD-2026-44027 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-07-14 microsoft GHSA-78c8-h6hm-94hg
7.8
CVSS 3.1 · Vendor: microsoft
Share

Severity by source

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

Authorized local attacker escalates privileges, so AV:L and PR:L with AC:L/UI:N; deserialization-driven code execution yields full C:H/I:H/A:H within unchanged scope.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/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
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Jul 14, 2026 - 17:58 vuln.today
CVE Published
Jul 14, 2026 - 17:05 nvd
HIGH 7.8

DescriptionCVE.org

Deserialization of untrusted data in Microsoft Exchange Server allows an authorized attacker to elevate privileges locally.

AnalysisAI

Local privilege escalation in Microsoft Exchange Server (2016 CU23, 2019 CU14/CU15, and Subscription Edition RTM) allows an already-authenticated attacker with low privileges to elevate to higher privileges by abusing unsafe deserialization of untrusted data. Microsoft reported the flaw and has released a patch; no public exploit identified at time of analysis and it is not listed in CISA KEV. The CVSS 3.1 base score is 7.8 (High), reflecting full confidentiality, integrity, and availability impact on the affected host.

Technical ContextAI

The vulnerability is rooted in CWE-502 (Deserialization of Untrusted Data), a class of bug where an application reconstructs objects from serialized input without validating type or content, allowing an attacker to influence object graphs and, on .NET platforms like Exchange, potentially trigger dangerous gadget chains during deserialization. Microsoft Exchange Server is a mail and calendaring platform built heavily on .NET, which historically has used serialization formats (e.g., BinaryFormatter, SoapFormatter, or ViewState-style payloads) that are susceptible to insecure deserialization. Per the supplied CPE data, the affected code is present in the on-premises builds cpe:2.3:a:microsoft:microsoft_exchange_server_2016_cumulative_update_23, microsoft_exchange_server_2019_cumulative_update_14, microsoft_exchange_server_2019_cumulative_update_15, and microsoft_exchange_server_subscription_edition_rtm, indicating the flaw spans multiple supported cumulative-update branches rather than a single build.

RemediationAI

Patch available per vendor advisory: apply the Microsoft security update for your Exchange build as documented at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55009 - the exact patched CU/SU version was not included in the provided data, so pull the specific update package for Exchange 2016 CU23, 2019 CU14, 2019 CU15, or Subscription Edition RTM from the MSRC page and verify build numbers before deployment. Because this is a local privilege-escalation vulnerability, compensating controls until patching include tightly restricting who can log on to or run code on Exchange servers (limit membership of local Administrators and Exchange management roles, enforce least privilege for service and delegated accounts), and enabling Windows Extended Protection and RBAC hardening per Microsoft's Exchange security guidance to shrink the set of accounts that could reach the vulnerable code path; the trade-off is added operational friction for administrators and third-party integrations that legitimately need elevated access. As a monitoring control, alert on unexpected process creation or SYSTEM-level activity spawned from Exchange worker processes, accepting that this is detection rather than prevention.

Share

CVE-2026-55009 vulnerability details – vuln.today

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