Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
Cybersecurity: Threats and Defences
7JUN

Exchange repeats the CISA deadline-before-patch trap

3 min read
10:08UTC

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
Causes and effects
This Event
Exchange repeats the CISA deadline-before-patch trap
Second deadline-before-patch ruling in twelve days. The pattern is now CISA posture rather than a one-off forced by exploitation velocity, and BOD 22-01's text has not been amended to acknowledge mitigation as compliance.
Different Perspectives
Australian Cyber Security Centre (ACSC)
Australian Cyber Security Centre (ACSC)
Australia's 18 of 95 May ransomware victims, nearly 19 per cent of global disclosed attacks against 0.3 per cent of global GDP, reflects end-of-life Windows Server concentration in healthcare, under-resourced national incident-response capacity, and time-zone isolation that slows vendor-assisted containment during peak attack windows.
Europol / international law enforcement
Europol / international law enforcement
Operation Saffron's 27-country coordination set a new geographic breadth record for criminal-infrastructure seizure. The absence of an arrest alongside the server seizures limits durable impact: VPNLab.net and DoubleVPN precedents show gangs reconstitute on alternative hosts within two to four weeks.
UK Parliament (Cyber Security and Resilience Bill)
UK Parliament (Cyber Security and Resilience Bill)
The Bill reaches Commons Report Stage on 10 June with penalties up to 4 per cent of global turnover. Qilin's NHS Synnovis attack in June 2024 and INC_RANSOM's Stuga Machinery posting on 5 June give the legislation a domestic evidence base connecting KEV-class exposure directly to UK CNI and supply-chain targeting.
German BSI / EU enterprise operator perspective
German BSI / EU enterprise operator perspective
The 17-month lag between Oracle's January 2024 WebLogic patch and active exploitation confirms that CVSS 7.5 keeps a flaw below emergency-patch thresholds in most programmes, even when T3/IIOP exploitation is a documented recurring chain. BSI's T3/IIOP disablement guidance offers a network-layer mitigation that survives Oracle's quarterly patch cycle without requiring unscheduled downtime.
ENISA / EU cybersecurity regulator
ENISA / EU cybersecurity regulator
NIS360's risk-zone designations for water and rail, following NCAF 2.0 in April, give member-state authorities a documented enforcement basis under NIS2. Fine ceilings at EUR 10 million cover essential entities; sub-threshold municipal water operators fall outside that scope, so designation without sector-level funding creates a perverse incentive to defer rather than remediate.
US federal CISO (FCEB agency)
US federal CISO (FCEB agency)
Four staggered June deadlines covered WebLogic middleware, Linux containers, Android device fleets and Magento storefronts in a single fortnight, forcing triage that exposes whichever stack ranks lowest. CISA's proposed $707 million budget cut alongside this enforcement acceleration creates a direct credibility gap: the mandate grows while the capacity to sustain it shrinks.