CVE-2026-42897: Microsoft Releases Emergency Mitigation for Microsoft Exchange XSS Vulnerability

Critical XSS Vulnerability (CVE-2026-42897) Threatens On-Premises Exchange Server

A serious cross-site scripting (XSS) vulnerability identified as CVE-2026-42897 has been discovered in the Outlook Web Access component of on-premises Exchange Server, with a critical CVSS score of 8.1. This flaw is currently being actively exploited, allowing unauthenticated attackers to execute arbitrary JavaScript code in a user’s browser simply by sending a malicious email. As of now, no permanent fix is available for Exchange 2016 and 2019.

Exchange Server has been a mainstay for email traffic across French organizations for years. The on-premises versions, particularly 2016, 2019, and the Subscription Edition, remain widely deployed in the public, healthcare, and industrial sectors, often operating well beyond the recommended update cycles. CVE-2026-42897 is part of a troubling trend of exploited OWA vulnerabilities in recent years, demonstrating that the attack surface of internally hosted email servers continues to be a prime target for malicious actors.

The vulnerability arises from inadequate input filtering in the Outlook Web Access component. When a user opens a specially crafted email in their OWA interface, Exchange Server renders content without properly filtering out tags and attributes that could carry JavaScript code. Consequently, an attacker can execute this code within the victim’s browser context, with the same privileges as their active session. This results in two immediate threats: bypassing configured security policies and allowing indirect remote code injection.

A Minimalist Yet Potent Attack Vector

The severity of CVE-2026-42897 lies in its simplicity. No prior access to the infrastructure, valid credentials, or sophisticated intrusion methods are required; the mere act of sending a malicious email suffices. Once the recipient opens the email in OWA, the embedded JavaScript executes in their browser. This execution occurs within the authenticated user’s session, enabling actions on their behalf such as mailbox data extraction, session token collection, redirection to malicious resources, or establishing persistent footholds within the environment.

Active exploitation has been confirmed by Microsoft shortly after the advisory’s release, suggesting that attackers likely knew about the vulnerability prior to its public disclosure—a hallmark of zero-day vulnerabilities targeting high-stakes email servers. On the same day, CERT-FR issued alert CERTFR-2026-ALE-005, categorizing the risks as security policy bypass and remote code injection, and recommending the immediate implementation of available mitigations.

However, a specific technical limitation restricts the attack’s reach: it does not work if the user accesses OWA via Internet Explorer or Microsoft Edge in Internet Explorer mode, as these browsers do not support the content security policy (CSP), a core mechanism for the bypass employed by Microsoft.

Exchange Emergency Mitigation Service: Operation and Limitations

In the absence of a permanent fix, Microsoft has activated an automatic mitigation through the Exchange Emergency Mitigation Service (EEMS) for Exchange 2016, 2019, and Subscription Edition servers. EEMS deploys a URL rewriting rule that blocks the request schema exploited by CVE-2026-42897, identified as mitigation M2.1.x. Administrators can verify its implementation via the Exchange console by checking active mitigations following Microsoft’s published guidelines.

For environments classified as “disconnected”—typically Exchange servers without Internet access, common in regulated, industrial, or defense sectors—automatic mitigation is not deployed. The Exchange team has shared a manual procedure for applying the mitigation on the Microsoft Tech Community blog, which necessitates intervention in the IIS configuration of the mailbox server. These disconnected environments are particularly vulnerable, as they not only lack automatic mitigation but often contain classified or mission-critical data.

Mitigation M2.1.x comes with several known effects. OWA’s calendar printing functionality becomes non-operational—a temporary workaround includes copying data or taking screenshots. Additionally, images embedded in emails may not render properly in the OWA reading pane, necessitating their attachment instead. OWA Light becomes unusable as well. While these degradations may be manageable in the short term for most environments, it is crucial to anticipate and communicate these issues to users prior to deployment.

A Distinct Divide Based on Versions and Support Contracts

The situation varies notably depending on the deployed Exchange version. For Exchange Server Subscription Edition, a permanent fix will be universally issued to all customers. However, for Exchange Server 2016 and 2019, the fix will only be distributed to organizations participating in the Extended Security Update (ESU) Program Period 2. Organizations whose ESU Period 1 subscriptions lapsed in April 2026 are not eligible for this fix and will not benefit through this channel.

This distinction creates a particularly vulnerable population—especially for organizations still operating Exchange 2016 or 2019 without subscribing to ESU Period 2. While they have the EEMS mitigation as a temporary safety net, they lack visibility on when a definitive fix will be available. For these environments, CVE-2026-42897 serves as a strong warning signal for the urgent need to plan a migration to Exchange Subscription Edition or Exchange Online—moves that can no longer be delayed indefinitely.

The issue of extended support highlights a broader systemic risk: maintaining obsolete or out-of-support email versions exposes organizations to vulnerabilities without guaranteed fixes, relying instead on partial mitigations prone to the side effects noted earlier. The NIS2 directive, effective in France with the Cyber Resilience Act of October 14, 2024, mandates that essential and important entities maintain their systems with an adequate security level relative to risks—criteria that the continued use of Exchange 2016 or 2019 outside of ESU Period 2 makes difficult to satisfy.

Priority Actions for IT Teams

The first step for IT teams is to verify the status of EEMS on each Exchange server. If the service is active and the server has Internet access, mitigation M2.1.x has been applied automatically. The verification procedure is outlined in Microsoft’s documentation under “Viewing Applied Mitigations.” For disconnected servers, the manual application of the URL rewriting rule described in the Exchange Team blog must be executed without delay.

Next, teams should map out the deployed versions and the active ESU contracts. Organizations lacking an ESU Period 2 subscription for Exchange 2016 or 2019 need to promptly engage in a risk assessment regarding the continued use of these versions and formally initiate discussions about planned migration. CERT-FR also recommends regularly reviewing vendor announcements for the availability of a permanent fix, which has yet to be disclosed.

Finally, security administrators can refer to the quick reference guides published by CERT-FR on email account compromise, qualification, and containment to prepare their response posture in the event that a user opens a malicious email prior to the implementation of the mitigation. Logging OWA access and reviewing active sessions should be immediate priority actions in environments that have not yet applied the mitigation.

Scroll to Top