CVE-2026-42897: Exchange Outlook Web Access cross-site scripting
Tech GuruQuick Answer
CVE-2026-42897 is cross-site scripting in on-premises Exchange Outlook Web Access: a crafted email can run JavaScript in the user's browser when the stated interaction conditions are met. It is not a claim of code execution on the Exchange server. Microsoft recommends the July 2026 security updates in the revised CVRF below. Verify every server and its mitigation state; Internet Explorer and Edge IE mode do not support the CSP-based protection.
Fix Or Immediate Action
What to do now: Install the newest applicable Exchange Server Security Update, verify every server, and keep the Exchange Emergency Mitigation Service operational where supported.
Evidence check: Vendor evidence and unresolved source limits are described below. CISA KEV catalog 2026.10.02 was checked on October 2. Preserve the distinction between vendor publication history, catalog dates and evidence from your deployment; no patch or exploit test is claimed.
Context
Scope And Impact In Plain Language
Who should check: Administrators of on-premises Exchange servers providing Outlook Web Access.
When this applies: Only when the exact product, version, and required configuration match the live vendor advisory. Owning the product family alone does not mean the device is vulnerable.
What could happen: A crafted page or request may run unwanted script in a user's browser as though it came from the affected, trusted website.
Not sure? Find the product name and version in the device or application, then compare them with the affected-products section of the linked vendor notice.
Status At A Glance
| Product scope | Microsoft Exchange Server / Outlook Web Access |
|---|---|
| CVE | CVE-2026-42897 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-05-15 |
| Vendor severity | Critical |
| CVSS | 8.1 (CVSS v3.1 base) |
| Ransomware field | Unknown — this is not the same as No; CISA has not marked the field Known. |
| Forensic-triage field | No in the current CISA field; organizations should still investigate when exposure or evidence warrants it. |
| CWE | CWE-79 |
| Federal remediation date | 2026-05-29 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
Microsoft Exchange Server Cross-Site Scripting Vulnerability. Microsoft Exchange Server contains a cross-site scripting vulnerability during web page generation in Outlook Web Access and when certain interaction conditions are met, arbitrary JavaScript can be executed in the browser context. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.
Affected Scope
On-premises Microsoft Exchange Server releases and Outlook Web Access configurations listed in the MSRC advisory.
Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.
Steps
What To Do Now
- Confirm. Inventory each on-premises Exchange server, its cumulative/security update level, OWA exposure and Exchange Emergency Mitigation Service state. Record the browsers used for OWA access.
- Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
- Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
- Remediate. Install the newest applicable Exchange Server Security Update, verify every server, and keep the Exchange Emergency Mitigation Service operational where supported.
- Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
- Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.
Fixed Releases And Mitigation
Permanent Fix
The July 14 FAQ revision recommends July 2026 Exchange Security Updates and says the EM/EOMT mitigation can be removed after those updates are installed. Do not remove it merely because an earlier update or the service itself is present. The revised Microsoft CVRF, checked October 2, supplies these exact product/update rows. Check current supersedence, entitlement and package prerequisites before installation; these are source checks, not deployment tests.
| Product and branch | Update | Fixed build |
|---|---|---|
| Microsoft Exchange Server 2016 Cumulative Update 23 | KB5094144 | 15.01.2507.069 |
| Microsoft Exchange Server 2019 Cumulative Update 14 | KB5094142 | 15.02.1544.041 |
| Microsoft Exchange Server 2019 Cumulative Update 15 | KB5094140 | 15.02.1748.046 |
| Microsoft Exchange Server Subscription Edition RTM | KB5094139 | 15.02.2562.043 |
Workaround Or Temporary Mitigation
Microsoft's Exchange Emergency Mitigation Service can deliver the supported mitigation, but verify its actual application on each server. The CVRF says Internet Explorer and Edge IE mode lack the required Content Security Policy support; do not use them for OWA. The service is not a substitute for the July security update, and removal of mitigation must follow successful update verification.
Important boundary: A workaround, access restriction, or provider-side control may reduce risk while the update is prepared, but it does not necessarily remove vulnerable code or erase an earlier compromise. Install the vendor-approved update when one is available.
Investigation And Recovery
A crafted message opened in Outlook Web Access can execute arbitrary JavaScript in the browser context when the stated interaction conditions are met. CISA lists the CVE as known exploited; review OWA, Exchange, authentication, and endpoint telemetry.
When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.
Notes
Exploitation Evidence
Vendor statement: Microsoft marked Exploited: Yes at original publication.
CISA statement: CVE-2026-42897 was added to KEV on 2026-05-15. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.
Validation And Boundaries
This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.
Related TechGeeks Resources
- TechGeeks Security Notice Center
- All Security Notices
- What to Do When a Device Hits CISA KEV
- Router CVE Exposure, Version, and Mitigation Checklist
- IoT Firmware Update and End-of-Support Checklist
- Live Protect and Runtime Vulnerability Shielding
References
- Microsoft security advisory
- Microsoft security advisory
- Microsoft security advisory
- NVD CVE record
- CISA source
Wrap-Up
Record whether CVE-2026-42897 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.
Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.
