Authenticated disclosure via server-side request forgery
Published Jun 9, 2026 · Updated Jun 9, 2026
Server-side request forgery in affected Microsoft Exchange Server releases allows remote authenticated users to expose data over a network. Microsoft identifies SSRF as the mechanism but has not disclosed the affected endpoint, request field, or backend request operation. A low-privileged Exchange account is required, and the published assessment limits the impact to confidentiality without integrity or availability effects.
Summary
What happened
Server-side request forgery in affected Microsoft Exchange Server releases allows remote authenticated users to expose data over a network. Microsoft identifies SSRF as the mechanism but has not disclosed the affected endpoint, request field, or backend request operation. A low-privileged Exchange account is required, and the published assessment limits the impact to confidentiality without integrity or availability effects.
The record
- CVE
- CVE-2026-45501
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Microsoft Exchange Server 2019 Cumulative Update 14
- Classifications
- CWE-918, CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=15.02.0.0 <15.02.1544.041
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo