3AUG

SharePoint patch clock runs out today

2 min read

16:08UTC

CISA gave federal agencies three days to remediate an actively exploited SharePoint code-execution flaw, with today's deadline the tightest on the catalogue.

← Back to KEV deadlines fell from 14 days to three Jump to analysis ↓

TechnologyDeveloping

Key takeaway

SharePoint's three-day KEV deadline lands today, the tightest federal patch clock of the fortnight.

CISA, the US federal cyber-defence agency, added CVE-2026-45659, a remote-code-execution (RCE) flaw in Microsoft SharePoint Server, to its Known Exploited Vulnerabilities (KEV) catalogue on Wednesday 1 July, with a Federal Civilian Executive Branch (FCEB) remediation deadline of today, Saturday 4 July. That is a three-day window on the most widely deployed on-premises collaboration platform across government and enterprise estates. The catalogue lists ransomware use as "Unknown". ¹

The flaw falls under BOD 26-04, the risk-tiered Binding Operational Directive that replaced patch-by-deadline enforcement on 10 June . A deserialisation-of-untrusted-data vulnerability lets an attacker feed crafted input that the server rebuilds into running code, and SharePoint's ubiquity across on-premises estates is what makes a three-day clock uncomfortable. Nothing else on the catalogue this fortnight runs tighter.

Deep Analysis

In plain English

SharePoint is a Microsoft tool that companies and governments use to share documents and manage internal websites. A flaw was found in the version installed on an organisation's own servers, rather than Microsoft's version, that lets an attacker send it corrupted data and gain control of the machine. The US government's cyber-defence agency ordered its own agencies to fix the flaw within three days of listing it, an unusually tight deadline, even though nobody has yet confirmed a ransomware gang is actively using it. The urgency comes from experience: a similar SharePoint flaw last year was used to break into government and manufacturing networks worldwide within about two weeks of becoming public.

Deep Analysis

Root Causes

CISA's BOD 26-04, which replaced the flat two-week patching mandate of BOD 22-01 on 10 June, sorts vulnerabilities into risk tiers with compressed deadlines for internet-facing remote-code flaws; a three-day window here is the tiering working as designed, not an emergency exception.

Many federal agencies still run SharePoint Server on-premises rather than the cloud version, often because of data-residency rules or a decade of custom workflow additions, which keeps a legacy deserialisation attack surface alive long after Microsoft's own roadmap pushed customers toward the hosted product.

What could happen next?

Risk
Agencies still running on-premises SharePoint Server face the same three-day clock regardless of patch-testing capacity, raising the odds some will remediate late, as happened with the Splunk and Ubiquiti deadlines this same fortnight (ID:4471, ID:4473).
Precedent
If exploitation follows the ToolShell timeline, ransomware use could move from Unknown to confirmed within two to three weeks of the 1 July listing.

Source Landscape

This story draws on neutral-leaning sources

Primary parallel: July 2025's 'ToolShell' SharePoint on-premises exploit chain (CVE-2025-53770) went from its exploited-vulnerability listing to mass ransomware use by the Warlock and Storm-2603 crews within roughly two weeks, hitting government and manufacturing targets worldwide.

Counter-parallel: 2019's SharePoint deserialisation bug, CVE-2019-0604, stayed confined to a handful of targeted espionage intrusions linked to the China-based APT27 group rather than becoming a mass event, because Microsoft's patch reached most customers before public proof-of-concept code circulated.

Consensus view: Rapid7's Caitlin Condon assesses that the three-day federal remediation window, 1 to 4 July, is unusually compressed for a deserialisation bug and reflects CISA applying its BOD 26-04 risk tiers aggressively, even though the catalogue entry itself lists ransomware use as Unknown.

Counter-view: China's Qihoo 360 Netlab team argues the compressed deadline reacts to confirmed exploitation rather than anticipating it, and notes that SharePoint's deserialisation flaw class has recurred since 2019 without Microsoft closing the underlying design pattern that keeps producing it.

Key tension: Whether a three-day remediation clock without a confirmed ransomware link protects agencies ahead of exploitation, or simply outruns their patch-testing cycles and pushes some to miss the deadline entirely.

Sources:CISA

Mentions:FCEB →Microsoft →China →CISA →CVE-2026-45247 →Microsoft SharePoint →BOD 26-04 →Rapid7 →Known Exploited Vulnerabilities →

First Reported In

Update #9 · FortiBleed harvest linked to Lynx crew

CISA· 4 Jul 2026

Read original →

Causes and effects

Caused by

CISA tears up its KEV deadline rules

BOD 26-04's risk-tiered framework set the remediation window applied to the SharePoint deserialisation flaw.

Occurred 10 Jun 2026

Read story →

This Event

SharePoint patch clock runs out today

A three-day deadline on the most widely deployed on-premises collaboration server is the first hard test of how fast agencies can move under the new triage regime.

Led to

SharePoint stays under active KEV fire

CISA's three-day SharePoint deserialisation KEV deadline set on 1 July is escalated by two further SharePoint deserialisation CVEs landing on 16 and 22 July.

Occurred 22 Jul 2026

Read story →

Different Perspectives

Group-IB

Group-IB, headquartered in Singapore, documented on 19 March that The Gentlemen began inside Qilin's own affiliate programme and split from it over a payment dispute. Its analysis makes this window's leak-site tally readable as a fracture inside one ransomware operation rather than the arrival of an unknown crew.

ENISA

ENISA placed EU drinking water and wastewater in its cyber risk zone for the first time on 28 May, finding one in three water entities had never run a risk assessment. CISA's 30 July advisory to American operators reads as the operational sequel to a gap European regulators had already documented two months earlier.

House of Lords and NCSC

The Cyber Security and Resilience Bill sits at House of Lords committee stage, its amendment paper running to 23 July. Separately, the NCSC guidance CISA cited when directing water operators to disconnect controllers is version 1.0 from March 2024, a two-year-old British document doing operational work in an American alert published last week.

heise online

heise online reported on 27 July that Russian state attackers, named as APT28, ran the hotel WiFi credential-harvesting campaign. Its attribution is firmer than ReliaQuest's own hedged low-to-medium confidence assessment of the same intrusion, a difference in national reporting posture rather than a settled dispute over who is responsible.

CISA and ReliaQuest

CISA compressed remediation deadlines under BOD 26-04 while, in the same window, telling water and wastewater operators to disconnect internet-exposed controllers rather than patch them. ReliaQuest, investigating the hotel WiFi campaign, held its assessment of the intrusion route at low-to-medium confidence and declined to name a state sponsor.

AIVD

AIVD co-signed AA26-204A alongside CISA, the NSA and the FBI, adding its signature to the fifteen-agency coalition naming LAUNDRY BEAR. Dutch involvement continues a pattern of joint Five Eyes-adjacent advisories the agency has co-issued with CISA and NCSC through 2026.