CVE-2025-53786

Microsoft Exchange Server Hybrid Deployment Elevation of Privilege Vulnerability

At a glance

Severity
HIGH 8.0
EPSS
EPSS 7.59 % · percentile 95 (2026-10-27)
State
PUBLISHED
Published
Updated
Assigner
microsoft
NVD status
Analyzed

Description

On April 18th 2025, Microsoft announced Exchange Server Security Changes for Hybrid Deployments and accompanying non-security Hot Fix. Microsoft made these changes in the general interest of improving the security of hybrid Exchange deployments. Following further investigation, Microsoft identified specific security implications tied to the guidance and configuration steps outlined in the April announcement. Microsoft is issuing CVE-2025-53786 to document a vulnerability that is addressed by taking the steps documented with the April 18th announcement. Microsoft strongly recommends reading the information, installing the April 2025 (or later) Hot Fix and implementing the changes in your Exchange Server and hybrid environment.

Scores

VersionScoreVectorScored by
CVSS 3.1HIGH 8.0CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:Cmicrosoft
CVSS 3.1HIGH 8.0CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HNVD · secure@microsoft.com (Secondary)

Weaknesses (CWE)

European references

CERT-FR advisories

Affected configurations (NVD CPE)

Affected products

ProductVersions
Microsoft · Microsoft Exchange Server 2016 Cumulative Update 23affected 15.01.0.0 < 15.01.2507.055
Microsoft · Microsoft Exchange Server 2019 Cumulative Update 14affected 15.02.0.0 < 15.02.1544.025
Microsoft · Microsoft Exchange Server 2019 Cumulative Update 15affected 15.02.0.0 < 15.02.1748.024
Microsoft · Microsoft Exchange Server Subscription Edition RTMaffected 15.02.0.0 < 15.02.2562.017

References

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD