CVE-2026-42897: Exchange OWA cross-site scripting exploited by TA488 with the OWAReaper implant; fixed since the June 2026 Security Update, which does not remove the mitigation
Exchange OWA flaw used in Russia-aligned espionage is fixed since June 2026, but its mailbox foothold needs removing
Defender actions
- Install the July 2026 Exchange Security Update on every on-premises Exchange 2016/2019/SE server, then explicitly remove the earlier CVE-2026-42897 mitigation, the EEMS M2.1.0 IIS rules or the EOMT script rollback, because the update does not remove either automatically.
- Audit mailbox folder permissions across the estate for Owner-level grants to the Exchange 'Default' alias and revoke them; this is the implant's server-side persistence and it survives password resets and endpoint re-imaging.
Analysis
CVE-2026-42897 is a cross-site scripting flaw in Outlook Web Access on Exchange Server 2016, 2019 and Subscription Edition; Microsoft scores it 8.1, marks it exploited (Microsoft Security Response Center, 2026-07-14), and CISA added it to its Known Exploited Vulnerabilities catalog on 2026-05-15 (CISA KEV catalog, 2026-05-15). Exchange Online is not affected (Microsoft Exchange Team Blog, 2026-05-14). Microsoft first protected on-premises servers with mitigation M2, a URL Rewrite configuration delivered by the Exchange Emergency Mitigation Service (Microsoft Learn). The EM service runs on Mailbox servers (installed with the September 2021 CU or later) and needs outbound HTTPS to officeclient.microsoft.com, which must also be excluded from SSL inspection; servers that cannot reach it never receive the mitigation, and Get-ExchangeServer | Format-List Name,MitigationsApplied shows what each server has applied (Microsoft Learn). A server running an Exchange Server build older than March 2023 cannot check for new mitigations at all (Microsoft Exchange Team Blog, 2026-05-14).
The fix shipped in the June 2026 Security Update (Microsoft Exchange Team Blog, 2026-06-09), and Microsoft recommends the July 2026 Security Update, which also addresses the related CVE-2026-55008; installing either does not remove the earlier mitigation, which stays in place until administrators remove it by hand (Microsoft Exchange Team Blog, 2026-06-09) (Microsoft Exchange Team Blog, 2026-07-14) (Microsoft Security Response Center, 2026-07-14). From 2026-07-22 Proofpoint observed TA488 (Void Blizzard, LAUNDRY BEAR) exploiting the flaw against government, telecommunications, finance, hospitality and aerospace targets in the US and Europe with the OWAReaper implant, whose server-side persistence survives password resets and re-imaging (Proofpoint, 2026-07-29); the update below carries the detail.
Cited evidence
The Exchange Emergency Mitigation Service will provide mitigation automatically, and is on by default.
The messages exploit CVE-2026-42897, a vulnerability in Outlook Web Access in which the server does not adequately sanitize HTML in the message body. This allows a loader piece of JavaScript to use the onload= event handler to parse the rest of the message body, assemble a Base64 fragment, and execute it as encoded JavaScript.
This persistent access lives on the server-side and requires deliberate removal from the Exchange server; credential rotation and even full re-imaging of the targeted user's device will not evict the actor.
Installing the July 2026 update does not automatically remove already applied CVE-2026-42897 mitigations.
Please note that EM Service will not be able to check for new mitigations if your server is running Exchange Server version older than March 2023
Updates4
CVE-2026-42897 was first an Exchange OWA flaw whose interim protection depended on the EM Service auto-mitigation. Two things changed. Proofpoint has now attributed in-the-wild exploitation to a named Russia-aligned actor and published the implant's full mechanics (Proofpoint, 2026-07-29), and the mitigation is no longer the remediation: the security updates are, with the mitigation now something Microsoft says administrators should remove (Microsoft Exchange Team Blog, 2026-07-14). NCSC-CH appended the Proofpoint reporting to its own advisory on 2026-07-30 (NCSC Switzerland, 2026-07-30).
The actor is TA488 (also tracked as Void Blizzard and LAUNDRY BEAR), the Russia-aligned email-espionage actor behind the Zimbra campaign that Proofpoint documented in a joint release with the NSA (Proofpoint, 2026-07-29). Proofpoint assesses OWAReaper as an evolution of that campaign's ZimReaper payload, citing shared code including the same sized, invisible pop-up and highly similar error handling (Proofpoint, 2026-07-29). Campaign activity began 2026-07-22 against government, telecommunications, finance, hospitality and aerospace targets across the US and Europe, using deliberately banal lure subjects with no call to action; Proofpoint says the unusual breadth may have been intentional blending with bulk mail. Its stated infrastructure-creation date of March 2026 precedes Microsoft's May disclosure by two months, which is the basis for its assessment that zero-day use is feasible; that is an inference from infrastructure dating, not a confirmed finding.
Execution. The flaw is a failure to sanitise HTML in the message body, so a loader script in an onload= handler reassembles a Base64 fragment from the rest of the message and evaluates it: no link click and no attachment open, only viewing the message in OWA. The exploit and payload fragments are hidden inside the message's social-media icon elements, with next-stage data placed after # fragment markers where the browser's Base64 image parser stops reading, so the payload is not visible to casual inspection of the HTML. On execution OWAReaper first rewrites the delivered message server-side to strip the exploit content and suppresses OWA pop-ups and right-click, then enumerates the victim's address, username and settings (Proofpoint, 2026-07-29).
Credential and token theft. It creates two invisible input elements and waits for the browser's own autofill to populate them with the saved OWA username and password. Separately it enumerates installed Outlook add-ins holding ReadWriteMailbox permission and, where one exists, abuses it to call GetClientAccessToken and obtain OAuth tokens (Proofpoint, 2026-07-29).
Persistence, in three independent layers. Client-side, the implant writes an encrypted copy of itself and a decryption wrapper into browser localStorage under a settings field of the legitimate PageDataPayload.OwaUserDefaultSettings key, which OWA itself evaluates during its own sync-restore flow, so every ordinary OWA tab-open re-launches it with no separate loader. A second client-side layer adds a hidden iframe to messages cached in OWA's offline IndexedDB store, so opening the cached message re-infects an endpoint even after a full re-image. The third is server-side and is the one that matters most: the implant calls UpdateFolder to grant Owner-level permission on every mail folder to the low-privilege "Default" preset alias that exists in every Exchange organisation. Proofpoint is explicit that this "requires deliberate removal from the Exchange server" and that credential rotation and re-imaging will not evict it (Proofpoint, 2026-07-29).
Command and control. Two channels, both over infrastructure defenders generally trust. The implant polls GitHub's public Commit Search API every 24 hours for crafted commit messages containing the target's own email address, decrypting matches to a four-character command header that selects toolkit replacement, C2-domain rotation, or one-off code execution; in parallel it re-parses cached inbound messages every five minutes for the same command structure. Exfiltration runs primarily over HTTPS with encrypted URI paths, either relayed through a set of legitimate image-CDN domains or sent directly to the actor-controlled server when those proxies fail; if the HTTPS method fails altogether, the implant switches to DNS label tunnelling, packing the data into the subdomain labels of ordinary DNS queries for an actor-controlled domain. Notably, Proofpoint states there is no mass mailbox exfiltration here, unlike the Zimbra campaign, so the mapped behaviour is browser-session and credential access rather than bulk email collection (Proofpoint, 2026-07-29).
Patching. The fix first shipped in the June 2026 Security Update (Microsoft Exchange Team Blog, 2026-06-09), and Microsoft now recommends the July 2026 Security Update, available as Exchange SE RTM publicly and for Exchange 2019 CU14/CU15 and Exchange 2016 CU23 only through the Period 2 Extended Security Update programme; organisations that were enrolled only in Period 1, which ended in April 2026 (Microsoft Exchange Team Blog, 2026-05-14), do not receive it (Microsoft Exchange Team Blog, 2026-07-14). Microsoft's own vulnerability record scores the flaw 8.1 and marks it exploited (Microsoft Security Response Center, 2026-07-14). Installing the update does not remove a previously applied mitigation: administrators who used the EM Service should remove the M2.1.0 IIS rules through the documented rollback, and those who ran the downloadable mitigation script should run its rollback (Microsoft Exchange Team Blog, 2026-07-14). The known operational side effects of the mitigation era (broken OWA calendar printing, inline-image rendering problems, OWA-light failing, and false-unhealthy calendar-proxy health alerts) are listed in the May post (Microsoft Exchange Team Blog, 2026-05-14), and the July post ties their clearing to installing the update and removing the mitigation (Microsoft Exchange Team Blog, 2026-07-14).
Triage: OWA legitimately reads and writes its own settings keys constantly, so the presence of localStorage activity is not the signal; the discriminator is the specific settings-field path carrying an encrypted blob, and its correlation with a message open. For the server-side artifact the discrimination is cleaner: administrators do grant folder permissions, but they grant them to named users or groups for a specific folder, not Owner rights to the built-in "Default" alias across an entire mailbox. Treat any such grant as compromise until proven otherwise.
The sourcing is the vendor's own advisory for its own product, independently corroborated: Proofpoint analysed the implant separately from Microsoft's disclosure, and NCSC-CH's post added a link to Proofpoint's analysis. Nothing in the assessment or the remediation guidance changed.
The EM service fetches mitigations from officeclient.microsoft.com over port 443, runs only on Mailbox servers, and reports applied mitigations through Get-ExchangeServer | Format-List Name,MitigationsApplied (Microsoft Learn); the earlier host name and Edge Transport cmdlet had no source. The fix first shipped in the June 2026 Security Update (Microsoft Exchange Team Blog, 2026-06-09), a month before the July update Microsoft now recommends (Microsoft Exchange Team Blog, 2026-07-14). Proofpoint describes its July 2026 report on the actor's Zimbra campaign as a joint release with the NSA (Proofpoint, 2026-07-29).
The Exchange Emergency Mitigation Service cannot check for new mitigations on a server running an Exchange Server build older than March 2023 (Microsoft Exchange Team Blog, 2026-05-14), so such a server did not receive mitigation M2 automatically.
Sources8
Revision history
- Published 2026-05-18-2eabc1cf
- Update 2026-07-31T0409Z-intel
Proofpoint attributed active exploitation of CVE-2026-42897 (the Outlook Web Access stored-XSS flaw Microsoft disclosed on 2026-05-14 and CISA KEV-listed on 2026-05-15) to TA488 (LAUNDRY BEAR / Void Blizzard), the Russian state-supported email-espionage actor that 16 nations jointly exposed on 2026-07-23 over a parallel Zimbra campaign. Merely opening a crafted message in OWA executes "OWAReaper", a JavaScript implant that runs entirely in the reading pane with no host file, harvests browser-autofilled OWA credentials, steals OAuth tokens through mailbox add-ins, and grants the Exchange "Default" alias Owner permission on every mail folder, server-side access that survives credential rotation and device re-imaging. Affected: on-premises Exchange Server 2016/2019/SE at any update level; Exchange Online is not in scope. The permanent fix is the July 2026 Exchange Security Update, and installing it does not remove the earlier mitigation artifacts.
Changed: actions affected_products cves entities evidence references regions sectors sources tags techniques body
- Improvement 2026-08-30T1312Z-audit
A first source-reliability rating, plus a serialization repair. The first action string was written as a double-quoted YAML scalar containing both a Windows-style path and escaped inner quotes, so a standards-compliant YAML parser rejected the whole frontmatter document; this repo's own lenient parser had always read the intended value. Re-quoted single so the backslash and the inner quotes stay literal. The stored value is byte-identical before and after, and no reader-facing text, claim or field value changed. The entry also carried no Admiralty rating, predating the always-classified gate; A1 is recorded, matching its sourcing: Microsoft's own advisory for its own product is A, and Proofpoint's independent analysis of the implant alongside Microsoft's disclosure is two parties who looked, so credibility 1.
Changed: actions classification
- Correction 2026-10-11T1307Z-audit
The title, summary, immediate action and first action named the wrong mitigation host (the EM service needs officeclient.microsoft.com), attributed the connectivity requirement to a blog note that only added a known issue, gave an undocumented verification cmdlet on the Edge Transport role where the EM service is not installed, and still said no fix existed. The fix first shipped in the June 2026 Security Update; Microsoft recommends the July update. The main analysis is rewritten to the current state with the EM-service mechanics from Microsoft Learn; the July section is corrected in place (June fix, the joint Proofpoint and NSA release instead of an uncited 16-nation advisory, no workflow vocabulary); an evidence quote is re-attributed to MSRC and one no longer on any cited page is removed; the mitigation-era immediate action and action are removed; priority moves from critical to high now that a fix has existed since June. The flaw is described as cross-site scripting, as Microsoft and Proofpoint describe it, not as stored XSS, and the 2026-07-31 takeaway now dates the fix to June. Exchange Online's exemption is cited to Microsoft's May blog, the 2026-07-31 section calls TA488 Russia-aligned as Proofpoint does, and event_date is the May advisory's date. The 2026-08-30 section is restated in plain language without rating codes. The title, headline and summary no longer say the mitigation must be removed by hand or that the foothold outlives patching: Microsoft says the update does not remove the mitigation, and Proofpoint says the mailbox grant needs deliberate removal. The body no longer says the mitigation must be rolled back or that the foothold outlives patching, the Period 1 end date is cited to the May blog, the 2026-07-31 mechanism paragraphs carry their Proofpoint citation, and the sector tags follow Proofpoint's targets.
Changed: title headline summary priority immediate_action tags cves sources evidence sourcing_note actions body event_date sectors
- Improvement 2026-10-21T1149Z-audit
Microsoft's May guidance says the Exchange Emergency Mitigation Service cannot check for new mitigations on a server running a build older than March 2023, so such a server never received the automatic mitigation. Proofpoint's two credential behaviours, browser-autofill harvesting and OAuth token theft through mailbox add-ins, are now mapped as credentials from web browsers and stolen application access tokens rather than unsecured credentials. The headline is shortened to the length limit without a change of meaning.
Changed: body evidence techniques headline
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.