CVE Tools

CVE-2026-45502

Microsoft Exchange Server Information Disclosure Vulnerability

No known exploitation. EPSS puts it in the 48th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

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 Microsoft Exchange Server version (2016 CU23, 2019 CU14, 2019 CU15, or Subscription Edition RTM) and note whether you are below the fixed update versions listed by Microsoft.
  2. If you are affected, update to the fixed versions: Exchange Server 2016 CU23 → 15.01.2507.069; Exchange Server 2019 CU14 → 15.02.1544.041; Exchange Server 2019 CU15 → 15.02.1748.046; Exchange Server Subscription Edition RTM (and Subscription Edition) → 15.02.2562.043.
  3. After updating, verify Exchange health and then review server/network logs for unusual outbound connections or request patterns around the Exchange server’s time of change.
  4. If patching is delayed, immediately limit/monitor accounts with low-level privileges on Exchange, and restrict any internal/external connectivity paths that could be abused for outbound requests (as allowed by your network design).

What it is

From the CVE record

Server-side request forgery (ssrf) in Microsoft Exchange Server allows an authorized attacker to disclose information over a network.

In plain language

Written by AI from the record

CVE-2026-45502 is an information-leaking flaw in Microsoft Exchange Server where a low-privileged user can trick the server into making network requests and revealing sensitive data; if you run Exchange and haven’t updated to the listed fixed updates, you should act.

CVE-2026-45502 is a server-side request forgery (SSRF) information-disclosure issue in Microsoft Exchange Server that allows an authorized attacker with low-level privileges to coerce the server into sending requests to arbitrary locations and leaking data over the network.

If you're affected

  • Sensitive customer email exposure
  • Credential/token or internal data leakage
  • Reputation and trust damage
  • Regulatory reporting risk

Exploitation

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

EPSS48th
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.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.

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

Attention now

Rising.

Lifecycle

15 events over 107 days, from the signal feeds we watch.

  1. EPSS band changemoderate → lowepss band change
  2. EPSS band changelow → moderate
  3. Patch availablerecord updated
  4. EPSS band changelow → moderateepss band change
  5. Patch availablerecord updated
  6. OpenVAS check added

Affected products

Technical detail

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

Scored 5.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 NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

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