CVE-2026-45502
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 · uneditedServer-side request forgery (ssrf) in Microsoft Exchange Server allows an authorized attacker to disclose information over a network.
In the news
Third-party coverage- Microsoft June 2026 Patch Tuesday fixes 6 zero-days, 200 flaws
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in Microsoft Exchange Server. An authenticated attacker can exploit this to make the Exchange server perform unauthorized network requests to internal or external resources, potentially exposing sensitive information. The CVSS score of 5 indicates moderate severity with network-based attack vector.
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= 2016= 2019< 15.02.2562.043CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Exchange Server versionRun 'Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion' in Exchange Management Shell, or check registry key 'HKLM\SOFTWARE\Microsoft\ExchangeServer\v15\SetupParameters' for installation versionAffected if Version is Exchange Server 2016, Exchange Server 2019, or Exchange Server Subscription Edition build less than 15.02.2562.043
-
Verify authentication configurationCheck OWA and ECP virtual directory authentication settings using 'Get-OwaVirtualDirectory | Format-List InternalAuthenticationMethods,ExternalAuthenticationMethods' and 'Get-EcpVirtualDirectory | Format-List AuthenticationMethods'Affected if Any authentication method is enabled that allows attacker to obtain valid user credentials
-
Confirm web interface exposureReview IIS bindings and firewall rules to determine if OWA/ECP endpoints are accessible from untrusted networks using 'Get-OwaVirtualDirectory | Select-Object InternalURL,ExternalURL'Affected if OWA or ECP is accessible from outside the trusted network perimeter
-
Check outbound network restrictionsReview firewall rules and proxy configurations to determine if Exchange server can make arbitrary outbound HTTP/HTTPS connectionsAffected if Server has unrestricted outbound network access allowing arbitrary HTTP requests
Your environment is affected if you run Exchange Server 2016, 2019, or Subscription Edition with a build below 15.02.2562.043 and the server is accessible to authenticated users with outbound network capabilities.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data15.02.2562.043
Apply Microsoft security updates for Exchange Server as soon as they become available. Additionally, implement network segmentation and restrict Exchange server network access to only necessary resources to limit the impact of SSRF exploitation.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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