dbcve.org
Exchange ServerApplication · Microsoft

CVE-2025-53782

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 15.02.2562.029 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect implementation of authentication algorithm in Microsoft Exchange Server allows an unauthorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Microsoft Exchange Server contains an incorrectly implemented authentication algorithm that allows an unauthorized local attacker to elevate privileges. This is a local privilege escalation vulnerability in the authentication mechanism.

MitigationApply Microsoft security updates for Exchange Server immediately upon release. Review access controls and monitor for suspicious local account activity as a defensive measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Exchange ServerApplication
Affected:= 2016= 2019
Exchange Server Subscription EditionApplication
Affected:< 15.02.2562.029

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Exchange Server version
    Open Exchange Management Shell and run: Get-ExchangeServer | Select-Object Name, AdminDisplayVersion, Version
    Affected if The version shown matches Exchange 2016 (any build), Exchange 2019 (any build), or Exchange Subscription Edition with build number less than 15.02.2562.029
  2. Verify exact build number via PowerShell
    Run Get-ExchangeServer | Format-List * in Exchange Management Shell to see detailed version information including the full build number
    Affected if The build number falls within any affected version range (2016, 2019, or Subscription Edition < 15.02.2562.029)
  3. Confirm Subscription Edition status
    Check if the server is running Subscription Edition by examining the product: Get-ExchangeServer | Select-Object Name, IsExchange2019UMAvailable, IsExchange2016UMAvailable
    Affected if Running Exchange Subscription Edition with version reported as less than 15.02.2562.029

Your environment is affected if Exchange Server 2016, Exchange Server 2019, or Exchange Subscription Edition with build below 15.02.2562.029 is installed, and an unauthorized local attacker could potentially exploit the authentication mechanism to escalate privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.02.2562.029 or later
Fixed in 15.02.2562.029
Interim mitigation

Apply Microsoft security updates for Exchange Server immediately upon release. Review access controls and monitor for suspicious local account activity as a defensive measure.

Recommended fix Moderate confidence

Exchange Server Subscription Edition 15.02.2562.029 or later; Exchange Server 2016 CU23 + latest SU; Exchange Server 2019 CU15 + latest SU

  1. Identify your current Exchange Server version by running Get-ExchangeServer | Format-List Name,AdminDisplayVersion in Exchange Management Shell
  2. For Exchange Server Subscription Edition: Apply the update to reach version 15.02.2562.029 or later from Microsoft Update/Catalog
  3. For Exchange Server 2016: Apply the latest Cumulative Update (CU23) and subsequently the latest Security Update
  4. For Exchange Server 2019: Apply the latest Cumulative Update (CU15) and subsequently the latest Security Update
  5. Verify successful installation by re-running Get-ExchangeServer and confirming the build number matches the patched version
  6. Restart the Exchange services if not done automatically by the installer
Caveat Standard Exchange Server update risks apply - test in non-production first; plan maintenance window as updates require service restart

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Exchange Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53782 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data