MicrosoftExploited incident
Exchange Server OWA cross-site scripting zero-day: mitigation May 14, patch June 9, 2026 (CVE-2026-42897)
CVE-2026-42897High, CVSS 8.1In CISA's Known Exploited Vulnerabilities catalog since 15 May 2026
- Exploited before a fix
Response
- Silence
- 0h First public report to first vendor statement
- Exposure
- 26d First public report to first fix
- Follow-through
- 26d First public report to a fix for every supported version
- Vendor silent
- Vendor statement, no fix
- Fixed for some versions
- Fixed when disclosed
- Date only, no time of day
Timeline and evidence
Open a moment to see its source and archived quote.
First public report
CVE-2026-42897 record (CNA: Microsoft)CuratedQuote verified
"datePublished":"2026-05-14T17:00:36.515Z"
Disclosed out of band (not on a Patch Tuesday) with 'Exploited: Yes' in Microsoft's CVE entry; no earlier public report was found.
- Source
- CVE-2026-42897 record (CNA: Microsoft) cve record
- Recorded time
- Precision
- To the minute
- Origin
- Curated. Found by a researcher, with a verbatim quote and link.
- Quote check
- Found in the archived copy
- Snapshot
sha256:9b38bf806c7f94fc…- Used in metrics
- Yes
6 more sources for this moment
Microsoft advisory CVE-2026-42897ClaimedQuote not found in archive14 May 2026
Microsoft Exchange Server Spoofing Vulnerability. Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Exchange Server allows an unauthorized attacker to
The vendor's own disclosure.
- Source
- Microsoft advisory CVE-2026-42897 vendor advisory
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Claimed. The date the source gives.
- Quote check
- Not found in the archived copy. Treat with caution.
- Snapshot
sha256:6bdb850cbdf1c060…- Used in metrics
- No, kept for the record
CVE.org record CVE-2026-42897ClaimedQuote verified14 May 2026, 17:00 UTC
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.
CVE record published.
- Source
- CVE.org record CVE-2026-42897 cve record
- Recorded time
- Precision
- To the minute
- Origin
- Claimed. The date the source gives.
- Quote check
- Found in the archived copy
- Snapshot
sha256:9b38bf806c7f94fc…- Used in metrics
- No, kept for the record
Bluesky postClaimedQuote not checked yet14 May 2026, 17:01 UTC
Addressing Exchange Server May 2026 vulnerability CVE-2026-42897 | Microsoft Community Hub! 🦋
Earliest third-party post we hold.
- Source
- Bluesky post social
- Recorded time
- Precision
- To the minute
- Origin
- Claimed. The date the source gives.
- Quote check
- Not checked yet
- Snapshot
- No archived snapshot
- Used in metrics
- No, kept for the record
CISA KEV (CVE-2026-42897)ClaimedQuote verified15 May 2026
Microsoft Exchange Server Cross-Site Scripting Vulnerability
Added to CISA's KEV catalog on 2026-05-15.
- Source
- CISA KEV (CVE-2026-42897) kev
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Claimed. The date the source gives.
- Quote check
- Found in the archived copy
- Snapshot
sha256:ef8fffede5c47200…- Used in metrics
- No, kept for the record
Mastodon postClaimedQuote not checked yet15 May 2026, 07:37 UTC
Microsoft Exchange Servers Targeted by Active CVE-2026-42897 Exploit Microsoft warns of a high-severity vulnerability, CVE-2026-42897, in its Exchange Servers, allowing attackers to spoof network communications via a cleverly
Earliest third-party post we hold.
- Source
- Mastodon post social
- Recorded time
- Precision
- To the minute
- Origin
- Claimed. The date the source gives.
- Quote check
- Not checked yet
- Snapshot
- No archived snapshot
- Used in metrics
- No, kept for the record
Hacker NewsClaimedQuote not checked yet16 May 2026, 20:09 UTC
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42897
Earliest third-party post we hold. An independent author on another platform posted within 48 hours. Used for unreviewed incidents only, never graded.
- Source
- Hacker News hn
- Recorded time
- Precision
- To the minute
- Origin
- Claimed. The date the source gives.
- Quote check
- Not checked yet
- Snapshot
- No archived snapshot
- Used in metrics
- No, kept for the record
Vendor statement
at disclosure
CVE-2026-42897 record (CNA: Microsoft)CuratedQuote verified
"datePublished":"2026-05-14T17:00:36.515Z"
- Source
- CVE-2026-42897 record (CNA: Microsoft) cve record
- Recorded time
- Precision
- To the minute
- Origin
- Curated. Found by a researcher, with a verbatim quote and link.
- Quote check
- Found in the archived copy
- Snapshot
sha256:9b38bf806c7f94fc…- Used in metrics
- Yes
2 more sources for this moment
Microsoft advisory CVE-2026-42897ClaimedQuote not found in archive14 May 2026
Microsoft Exchange Server Spoofing Vulnerability. Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Exchange Server allows an unauthorized attacker to
- Source
- Microsoft advisory CVE-2026-42897 vendor advisory
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Claimed. The date the source gives.
- Quote check
- Not found in the archived copy. Treat with caution.
- Snapshot
sha256:6bdb850cbdf1c060…- Used in metrics
- No, kept for the record
Exchange Team blog: Addressing Exchange Server May 2026 vulnerability CVE-2026-42897 (Wayback capture 2026-05-15)CuratedQuote verified14 May 2026
On May 14, 2026, Microsoft disclosed
Opening sentence: 'On May 14, 2026, Microsoft disclosed CVE-2026-42897, a reported vulnerability affecting Exchange Outlook Web Access (OWA).' (re-quoted 2026-10-23 so the quote does not cross the CVE link markup).
- Source
- Exchange Team blog: Addressing Exchange Server May 2026 vulnerability CVE-2026-42897 (Wayback capture 2026-05-15) vendor blog
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Curated. Found by a researcher, with a verbatim quote and link.
- Quote check
- Found in the archived copy
- Snapshot
sha256:1f7c022866162828…- Used in metrics
- No, kept for the record
First workaround
date onlysame day
Exchange Team blog: Addressing Exchange Server May 2026 vulnerability CVE-2026-42897 (Wayback capture 2026-05-15)CuratedQuote verified
Customers with EM Service enabled can verify that their servers have applied the mitigation for CVE-2026-42897 (the ID of mitigation is M2.1.x) by doing the following:
Mitigation M2.1.x via the Exchange Emergency Mitigation Service (on by default) or the EOMT script, published with the disclosure on 2026-05-14. The post states 'Microsoft is working on and will release and announce a security update for impacted versions of Exchange Server in the future.'
- Source
- Exchange Team blog: Addressing Exchange Server May 2026 vulnerability CVE-2026-42897 (Wayback capture 2026-05-15) vendor blog
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Curated. Found by a researcher, with a verbatim quote and link.
- Quote check
- Found in the archived copy
- Snapshot
sha256:1f7c022866162828…- Used in metrics
- Yes
First fix
date only+26d
Microsoft Support KB5094139 (Exchange SE RTM)CuratedQuote verified
Description of the security update for Microsoft Exchange Server Subscription Edition RTM: June 09, 2026 (KB5094139)
The KB lists CVE-2026-42897 among the CVEs it resolves. MSRC CVRF revision 2.0 (2026-06-09): 'Added links to June 2026 Exchange Server security updates.'
- Source
- Microsoft Support KB5094139 (Exchange SE RTM) vendor advisory
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Curated. Found by a researcher, with a verbatim quote and link.
- Quote check
- Found in the archived copy
- Snapshot
sha256:180b1a2b6838567e…- Used in metrics
- Yes
1 more source for this moment
Microsoft advisory CVE-2026-42897ClaimedQuote verified14 May 2026
Information published.
Vendor Fix listed at the first revision
- Source
- Microsoft advisory CVE-2026-42897 vendor advisory
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Claimed. The date the source gives.
- Quote check
- Found in the archived copy
- Snapshot
sha256:c8e475f7b6a3cbff…- Used in metrics
- No, kept for the record
Fixed for all versions
date only+26d
Microsoft Support KB5094144 (Exchange 2016 CU23)CuratedQuote verified
Description of the security update for Microsoft Exchange Server 2016 CU23: June 09, 2026 (KB5094144)
2019 CU15 (KB5094140) and CU14 (KB5094142) are also dated June 09, 2026. The Exchange team said 2016 and 2019 updates go only to Period 2 ESU customers ('Exchange 2016 and 2019 updates will be released only to customers who are enrolled in the Period 2 Exchange Server ESU program'), since those versions are past mainstream support.
- Source
- Microsoft Support KB5094144 (Exchange 2016 CU23) vendor advisory
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Curated. Found by a researcher, with a verbatim quote and link.
- Quote check
- Found in the archived copy
- Snapshot
sha256:e213dabad9e2d8a2…- Used in metrics
- Yes
1 more source for this moment
Microsoft advisory CVE-2026-42897ClaimedQuote verified14 May 2026
Information published.
every Known Affected product has a Vendor Fix and no later revision announces more updates
- Source
- Microsoft advisory CVE-2026-42897 vendor advisory
- Recorded time
- Precision
- Date only (no time of day is shown)
- Origin
- Claimed. The date the source gives.
- Quote check
- Found in the archived copy
- Snapshot
sha256:c8e475f7b6a3cbff…- Used in metrics
- No, kept for the record
Send this to your boss
No brief for this incident yet. We write one for every open incident and every critical bug exploited before a fix.
Affected products
- Microsoft Exchange Server Subscription Edition RTM
- Exchange Server 2019 CU14 and CU15 (ESU)
- Exchange Server 2016 CU23 (ESU)
How we built this timeline
Selected as a patch-day exception: exploited zero-day disclosed out of band with a mitigation only; the security update came 26 days later on June 2026 Patch Tuesday, so 'disclosed and fixed in the same release' would be wrong. R1 decision (correction pass 23 Oct 2026): the June 9, 2026 update is kept as the complete fix.
On 14 Jul 2026 Microsoft added to this CVE's FAQ: 'Mitigations that have been applied either using the Exchange Emergency Mitigation Service or the EOMT script can be removed after July 2026 update is installed.' The reason is a different bug: CVE-2026-55008 (published 14 Jul 2026, CVSS 9.6, 'Exploited:No', not in KEV) is a separate OWA cross-site scripting flaw, and its FAQ says 'Customers who have installed the July 2026 Security Updates on all affected Exchange servers are fully protected and may safely remove the CVE-2026-42897 mitigation (which is similar in nature and mitigates CVE-2026-55008 also).' Microsoft never describes the June update as incomplete for CVE-2026-42897: this CVE's revision 2.0 (9 Jun 2026) 'Added links to June 2026 Exchange Server security updates', its update table still lists the June KBs (5094139/40/42/44), and the June KBs list CVE-2026-42897 as resolved. R7 does not merge CVE-2026-55008: it is not reported as exploited or chained, and was disclosed 61 days later.
Microsoft notes Internet Explorer / IE mode are not protected by the CSP-based mitigation. CVSS 8.1 from Microsoft.
KEV added 15 May 2026.
Related
- Defender Link Following Vulnerability CVE-2026-41091
- Defender Denial of Service Vulnerability CVE-2026-45498
- SharePoint Server Deserialization of Untrusted Data Vulnerability CVE-2026-45659