Skip to content
Welcome, thoughtbot's Giant Robots listeners!Start here
Cybersecurity: Threats and Defences
12OCT

Exchange repeats the CISA deadline-before-patch trap

3 min read
10:55UTC

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
ENISA
ENISA
ENISA's 22 September threat report found only 23.8 per cent of NoName057(16)'s assessed claims were confirmed by independent availability checks, though the group produced 48 per cent of ideology-driven activity. The agency's numbers show public administration taking 31.8 per cent of attacks, mostly ideological DDoS.
LKA Hamburg
LKA Hamburg
Hamburg's State Criminal Police Office led the operation that took the KillSec leak site on 30 September, with ten countries, Europol and Eurojust. Investigators link the group to around 1,000 suspected attacks, at least 70 in Germany, and the seizure blocks access to at least 110 terabytes of victims' data.
ASOS
ASOS
ASOS said an unauthorised party reached names and contact details on third-party platforms after obtaining an employee's credentials by impersonating a trusted contact. It said it does not believe payment cards or account passwords were affected, and is investigating.
Check Point
Check Point
Check Point updated its advisory on 20 September to say its 9.8-rated VPN certificate flaw had been exploited on Spark firewalls since 12 September, five days after the advisory first appeared, and shipped fixes including R81.20 Take 166. It told customers using only pre-shared-key VPN communities they were not exposed.
Japan's National Police Agency
Japan's National Police Agency
Japan's National Police Agency and National Cybersecurity Office signed advisory AA26-281A and published it on 9 October, naming SoftEther VPN, MicroScan and office-cli and indicators detected since January 2016. Tokyo says the evidence comes from several FBI criminal investigations and that it will deepen cooperation with allies.
CISA
CISA
CISA gave federal agencies three days to fix five flaws from 2015 to 2023 on the day the China advisory named Integrity Technology Group, and set the same clock on 34 of 43 September listings. It treats a named state-linked operation as reason enough to patch old software within the week.