Skip to main content
Mallory
MediumCISA KEVExploited in the wild1 public exploit

Reflected XSS in Microsoft Exchange OWA

CVE-2026-42897 is an actively exploited cross-site scripting vulnerability in on-premises Microsoft Exchange Server, specifically affecting the Outlook Web Access (OWA) component. The flaw stems from improper neutralization of input during web page generation. Available reporting indicates the vulnerable OWA server-side rendering logic embeds user-controlled values, including URL paths or query string parameters, into generated HTML without context-aware output encoding. As a result, a specially crafted email or reflected input can cause attacker-controlled JavaScript to execute in the victim’s browser when the content is opened in OWA under certain interaction conditions. Microsoft describes the issue as a spoofing vulnerability rooted in XSS. Affected products include Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition on-premises at any update level; Exchange Online is not affected.

Share:
Stay ahead

Get ahead of vulnerabilities like this

Mallory continuously monitors global threat intelligence and correlates it with your attack surface — so you know if you’re exposed before adversaries strike.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. For analysts and engineers who need to decide and keep moving.

Impact

What an attacker gets — and what they’ve been doing with it.

Successful exploitation allows arbitrary JavaScript execution in the security context of the trusted OWA origin within the victim’s browser session. This enables spoofing of the Exchange web interface and can expose sensitive data available to that session, including mailbox content and potentially session artifacts accessible from the browser context. Reported downstream risks include credential harvesting, session manipulation or token theft, phishing amplification, and other user-context actions within OWA. The CVSS information provided indicates high confidentiality and integrity impact, with no direct availability impact. Public reporting does not describe this CVE itself as direct server-side code execution.

Mitigation

If you can’t patch tonight, do this now.

Ensure EEMS is enabled and functioning on supported on-premises Exchange deployments so the URL Rewrite-based emergency mitigation is applied automatically. Verify mitigation status using Exchange Health Checker, applied mitigation listings, or EEMS logs, including confirmation that mitigation ID M2/M2.1.x is applied. In environments where EEMS cannot reach Microsoft, manually deploy the mitigation with EOMT. Until a permanent patch is available, prioritize externally reachable OWA-enabled servers, monitor OWA access and authenticated activity following email opens, and watch for signs of credential harvesting or suspicious browser-driven actions. Administrators should also account for known mitigation side effects, including broken OWA calendar printing, incorrect inline image rendering, and issues with deprecated OWA Light.

Remediation

Patch, then assume compromise.

Apply Microsoft’s official mitigation immediately via the Exchange Emergency Mitigation Service (EEMS), which Microsoft states has published mitigation M2/M2.1.x for this issue using a URL Rewrite configuration. For disconnected or air-gapped environments, use the latest Exchange On-Premises Mitigation Tool (EOMT) to apply the CVE-2026-42897 mitigation manually. Microsoft has stated that a permanent security update is being developed for Exchange SE RTM, Exchange 2016 CU23, and Exchange Server 2019 CU14/CU15; organizations running older cumulative updates should upgrade to supported levels in preparation. Exchange 2016 and 2019 customers require the applicable Period 2 ESU entitlement to receive the future fix.
PUBLIC EXPLOITS

Exploits

No valid public exploits — Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView all

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationExchange Serverapplication
Microsoft CorporationExchange Server 2016application
Microsoft CorporationExchange Server 2019application
Microsoft CorporationExchange Server Seapplication

Vendor-confirmed product mapping. Mallory continuously reconciles against your asset inventory in the product.

ACTIVITY FEED

Recent activity

172 sources tracked across advisories, community write-ups, and news. Mallory keeps watching after this page renders.

172 SOURCESView all
The operational view lives in Mallory

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t — which of your assets are affected, which threat actors are using it right now, which detections to deploy, and what to do next.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules — auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity154

Community discussion across Reddit, Mastodon, and other social sources.