CVE Tools

CVE-2026-62911

Microsoft Exchange Server Elevation of Privilege Vulnerability

No known exploitation. EPSS puts it in the 51st percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check your Exchange Server version against the fixed versions listed by Microsoft (see “what_to_do_full” for the exact numbers).
  2. If you’re on any affected version, upgrade immediately to the Microsoft fixed version for your branch: Subscription Edition → 15.02.2562.046; Exchange 2016 CU23 → 15.01.2507.072; Exchange 2019 CU14 → 15.02.1544.044; Exchange 2019 CU15 → 15.02.1748.049.
  3. If you cannot upgrade right away, stop exposing Exchange services to the public internet as much as possible and tightly restrict network access to Exchange to only required clients and admin networks until the upgrade is done.
  4. After upgrading, verify the Exchange build reports the target fixed version and review Exchange security-related logs for suspicious privilege changes.

What it is

From the CVE record

Authentication bypass by capture-replay in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.

In plain language

Written by AI from the record

CVE-2026-62911 is a Microsoft Exchange Server security flaw that can let an authenticated attacker gain higher privileges over the network; if you run Exchange, you should fix it now.

Microsoft Exchange Server Elevation of Privilege (CVE-2026-62911) is an authentication bypass that can be triggered via capture-replay, allowing a network attacker who has some valid access to elevate privileges.

If you're affected

  • Full email system takeover risk
  • Account and mailbox compromise
  • Admin-level control of Exchange
  • Service disruption from malicious changes

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS51st
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.7% chance of exploitation activity in the next 30 days, which ranks it in the 51st percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

13 events over 22 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. OpenVAS check added
  4. Patch availablerecord updated
  5. Record updatedrecord updated
  6. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

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

Scored 8.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store