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

Reflected XSS in Microsoft Exchange Server OWA

CVE-2026-42897 is an actively exploited cross-site scripting vulnerability in on-premises Microsoft Exchange Server, specifically affecting Outlook Web Access (OWA). The issue stems from improper neutralization of input during web page generation. Available reporting indicates the vulnerable OWA server-side rendering logic reflects attacker-controlled input, including URL paths or query string parameters, into generated HTML without context-aware output encoding. Multiple sources also state the attack can be delivered via a specially crafted email; when the victim opens the email in OWA and certain interaction conditions are met, arbitrary JavaScript executes in the browser context of the trusted Exchange/OWA origin. Microsoft characterizes the issue as enabling spoofing over a network. Affected products include Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition on premises; 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 attacker-supplied JavaScript to run in the victim's OWA browser session under the legitimate Exchange origin. This can enable spoofing, DOM manipulation, session hijacking or token theft, credential harvesting, phishing amplification, access to mailbox content available in-session, and other user-context actions within OWA. Reported CVSS characteristics and vendor descriptions indicate high confidentiality and integrity impact, with no direct availability impact. The flaw is confirmed exploited in the wild and has been added to CISA's Known Exploited Vulnerabilities catalog.

Mitigation

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

Ensure the Exchange Emergency Mitigation Service is enabled and functioning so mitigation M2/M2.1.x is applied automatically. Verify mitigation status via Exchange Health Checker, applied mitigation status, or EEMS logs under %ExchangeInstallPath%\Logging\EmergencyMitigation. In environments where EEMS cannot reach Microsoft, apply the mitigation with EOMT. Prioritize externally reachable on-prem OWA systems, monitor OWA access and suspicious post-email-open activity, and keep the mitigation in place until Microsoft releases the permanent update. Be aware of known 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 vendor mitigation immediately and monitor for the permanent security update when released. Microsoft states the temporary protection is delivered automatically through the Exchange Emergency Mitigation Service (EEMS/EM Service) as mitigation M2 via a URL Rewrite configuration for supported Exchange Server 2016, 2019, and Subscription Edition deployments. 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 fix is being developed for Exchange SE RTM, Exchange 2016 CU23, and Exchange Server 2019 CU14/CU15; customers on older cumulative updates should upgrade now to be eligible/apply the final fix when available.
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

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

174 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 activity156

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