Skip to content
You can now search across every topic, entity and event.What's new
Cybersecurity: Threats and Defences
14JUN

Exchange repeats the CISA deadline-before-patch trap

3 min read
11:51UTC

CISA added Exchange Server CVE-2026-42897 to KEV on 15 May with a 29 May federal deadline before Microsoft had shipped a patch, leaving on-premises operators with only the Exchange Emergency Mitigation Service URL-rewrite as a compliance route.

TechnologyDeveloping
Key takeaway

Federal agencies must mitigate, not patch, Exchange OWA by 29 May under a directive that does not allow it.

CISA added CVE-2026-42897, a cross-site scripting zero-day in Microsoft Exchange Server's Outlook Web Access (OWA), to its Known Exploited Vulnerabilities catalogue on Friday 15 May 2026 with a federal remediation deadline of Friday 29 May. The vulnerability scores CVSS 8.1. Microsoft had not shipped a patch at the time the deadline was issued; the only available mitigation was the Exchange Emergency Mitigation Service (EEMS) URL-rewrite rule. Active exploitation was confirmed against on-premises Exchange Server 2016, 2019, and Subscription Edition. Exchange Online is unaffected 1 2.

CISA has now issued two deadline-before-patch rulings inside twelve days. The PAN-OS CVE-2026-0300 KEV addition on 6 May established the first such case, where Palo Alto's first patches shipped four days after CISA's federal deadline. Twelve days later, CISA repeated the move on Exchange. Binding Operational Directive 22-01, the 2021 instrument that gives the KEV catalogue federal force, was drafted on the assumption that remediation existed. Its text has not been amended to recognise mitigation as a compliance route, and Microsoft's own EEMS guidance carries documented side effects to OWA calendar, Light mode, and inline images. For federal civilian Chief Information Officers running on-premises Exchange, compliance now means accepting a degraded mail experience to satisfy a directive that does not formally contemplate the route they are taking.

Microsoft Intune, the company's mobile-device management product, has surfaced repeatedly in the 2026 KEV stream alongside its Exchange and OS estate. Outside the federal civilian executive branch the KEV is voluntary, but the ICO's Capita ruling treated NCSC guidance as enforceable GDPR baseline, and a US KEV deadline carries the same shape under UK and EU data-protection frameworks. The CISA directive may be federal in scope; its enforceability is now international by precedent.

Deep Analysis

In plain English

US government agencies were told on 15 May 2026 that they must fix a serious security flaw in Microsoft's email server software by 29 May. The catch: Microsoft had not released a fix yet. Agencies could only reduce the risk using a workaround that also broke some email features.

Deep Analysis
Root Causes

Microsoft's on-premises Exchange Server architecture accumulates complexity across three product versions, 2016, 2019, and Subscription Edition, with different patch cadences and mitigation compatibility profiles.

The Exchange Emergency Mitigation Service was introduced in 2021 as an emergency response to ProxyLogon, indicating Microsoft anticipated recurring zero-day exposure in the on-premises product; the EEMS approach trades functional degradation, OWA calendar, Light mode, and inline images, for rapid deployment without full patch testing.

The structural cause of repeat Exchange zero-days is the product's age and the depth of its Windows-kernel and IIS-pipeline integration, which creates a large attack surface that each new feature addition extends.

Exchange Online's immunity to CVE-2026-42897 reflects a different deployment model: Microsoft controls the infrastructure and applies mitigations centrally without customer action, illustrating that the on-premises exposure is partly an architectural legacy problem rather than purely a code quality issue.

First Reported In

Update #4 · AI joins the breach column on both sides

Cybersecurity and Infrastructure Security Agency· 20 May 2026
Read original
Different Perspectives
Beijing-aligned attribution sceptics
Beijing-aligned attribution sceptics
CNCERT has noted that Western KEV ransomware-risk flags on DoS-only flaws such as Serv-U CVE-2026-28318 conflate disruption capability with breach capability, and that CJEU referrals for NIS2 non-transposition create compliance obligations that presuppose software-patchable architectures the Arista case shows are not universal.
Enterprise security buyers
Enterprise security buyers
Three successive KEV cycles in which federal deadlines precede, exceed or are refused by vendor patches require buyers to re-weight patch-SLA contractual terms: the KEV deadline is now the planning constraint, not the vendor advisory, and procurement due diligence must cover whether a hardware platform is even patchable in principle.
Check Point
Check Point
Check Point disclosed CVE-2026-50751 and shipped a hotfix on 8 June, roughly 30 days after exploitation had begun, with a Qilin affiliate already inside at least one victim. Its delayed disclosure on a CVSS 9.3 perimeter bypass leaves customers to absorb a month-long pre-patch exposure window under CISA's three-day federal deadline.
European Commission and ENISA
European Commission and ENISA
NIS2 full personal-liability enforcement from 1 June and CJEU referrals against laggard member states represent the sharpest regulatory escalation in EU cyber history, backed by ENISA NIS360 sector-maturity evidence naming water, rail and waste water as the priority enforcement targets. NCAF 2.0 and NIS360 function as audit instruments rather than political signals.
UK NCSC
UK NCSC
The NCSC issued the Dutch NCSC's imminent-abuse warning on the Check Point flaw in the same fortnight its sponsoring legislation cleared the Commons, widening incident-reporting duties to cover attacker pre-positioning. The payment-reporting gap left by the CS&R Bill means the NCSC continues to rely on voluntary Early Warning submissions for ransomware economics data.
US Federal CISO community
US Federal CISO community
Federal CISOs face three active compliance obligations without a clean resolution: a three-day Check Point deadline met with a hotfix, a 23 June Arista deadline partially met with ACLs only, and a 16-day Exchange overrun still being fully remediated. BOD 22-01 is operating as an urgency signal but not as a vendor-cooperation mechanism.