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

CISA tears up its KEV deadline rules

4 min read
12:09UTC

CISA revoked BOD 22-01 on 10 June and replaced it with a risk-tiered model, four days before Arista's deadline under the old order fell due.

TechnologyDeveloping
Key takeaway

The federal patch-deadline era ended because exploitation outran it, not because anyone won the argument.

The US Cybersecurity and Infrastructure Security Agency (CISA) revoked BOD 22-01 (Binding Operational Directive 22-01) on 10 June and replaced it with the risk-tiered BOD 26-04⁠1. BOD 22-01 had been the order behind CISA's mandatory patch deadlines for US federal agencies since 2021, built on the agency's catalogue of KEV (Known Exploited Vulnerabilities), its list of flaws confirmed as actively exploited. Under the new directive, agencies no longer get one due date per flaw. They score each one across four dimensions, asset internet exposure, KEV catalogue status, exploit-automation feasibility, and post-exploitation impact, then assign a 3-day, 14-day, 60-day, or next-upgrade-cycle window⁠2. The KEV catalogue had passed 1,627 entries by 23 June, roughly two new flaws a day to triage under the new rules⁠3.

The shift answers a problem this beat has tracked for four months: deadlines outrunning the patches meant to meet them. CISA set a PAN-OS deadline that landed four days before the patch shipped; it listed an Exchange OWA flaw with a federal cut-off and no fix at all; and on 9 June Arista Networks formally refused to patch a KEV-listed flaw, leaving agencies bound to remediate something the vendor would not repair. BOD 22-01 assumed a patch existed or was imminent, and had no answer for any of those cases.

The transition carries a live irony. Arista's 23 June deadline, now passed, was set under a directive CISA had already revoked on 10 June. Whether it still bound federal Arista customers after the revocation was never resolved in public, and CISA has named no enforcement action since it lapsed.

Treat the reframe with care. BOD 26-04 maps closely onto what CISA already did case by case, since Check Point drew a 3-day window and Arista 14 under the old order⁠4. The new directive still carries no explicit clause for a vendor that declines to patch outright, so the Arista problem is reclassified into the risk tiers rather than closed. Revoking the foundational directive is materially significant; the claim that it ends the patch-gap era is not.

Deep Analysis

In plain English

CISA is the US government agency responsible for telling federal departments and agencies which software vulnerabilities they must fix, and how fast. Until 10 June 2026, the rule was simple: once a flaw went on its official list (called the Known Exploited Vulnerabilities catalogue), agencies had a fixed window, usually 14 days, to patch. The new rule, BOD 26-04, asks: how dangerous is this specific flaw, in this specific situation? A flaw that is being actively attacked on the internet, can be exploited automatically, and gives the attacker full control of a system gets three days. A less severe flaw with no evidence of active exploitation might get 60 days or simply the next planned upgrade. The idea is to focus urgent effort where risk is highest, rather than treating every flaw identically.

Deep Analysis
Root Causes

BOD 22-01 collapsed under three converging pressures. First, the fixed-deadline model assumed vendors would patch before federal deadlines, a premise that broke publicly when the PAN-OS CVE-2026-0300 deadline preceded the patch by four days , and again when CISA listed Exchange CVE-2026-42897 with no remediation path .

Second, Arista's confirmed refusal to patch CVE-2026-7473 exposed the absence of any enforcement mechanism against non-cooperative vendors: the directive bound federal agencies, not the vendors supplying them.

Third, the KEV catalogue grew 42 entries since late April to reach 1,627, generating a volume of deadlines that CISA could not monitor for compliance after the Trump FY27 budget proposed cutting the agency by $707 million and 860 positions. A smaller agency faced with more deadlines produces selective enforcement; risk-tiering is partly a staffing adaptation.

What could happen next?
  • Risk

    In-flight BOD 22-01 deadlines, including Arista's 23 June window, entered a period of transitional ambiguity on 10 June; federal agencies that were tracking these deadlines now lack a clear compliance posture until CISA publishes BOD 26-04 classification guidance.

    Immediate · Assessed
  • Consequence

    Cyber insurers and procurement auditors using KEV status as a mandatory-patch proxy must rebuild their assessment templates; the existing 14-day default is no longer universal.

    Short term · Reported
  • Precedent

    BOD 26-04 is the first US federal directive to formally codify risk-tiered vulnerability remediation; if it reduces patch cycle time for the highest-severity flaws, it will become the model for allied-nation NIS2 and NCSC guidance updates.

    Medium term · Suggested
First Reported In

Update #8 · CISA tears up the KEV deadline rulebook

CISA· 24 Jun 2026
Read original →
Causes and effects
This Event
CISA tears up its KEV deadline rules
The benchmark every federal and enterprise patch programme calibrates against has changed from a single deadline per flaw to a four-dimension risk score.
Led to
Triple CVSS-10 Ubiquiti chain hits root
BOD 26-04's 3-day top tier is first operationalised by the Ubiquiti KEV batch on 23 June, making this the new regime's debut in the wild.
Occurred 23 Jun 2026
Read story →
SharePoint patch clock runs out today
BOD 26-04's risk-tiered framework set the remediation window applied to the SharePoint deserialisation flaw.
Occurred 1 Jul 2026
Read story →
BOD 26-04, a fortnight of triage
BOD 26-04 is the risk-tiered directive whose first fortnight this event quantifies.
Occurred 4 Jul 2026
Read story →
A quiet KEV fortnight, then a 2008 bug
BOD 26-04's risk-tiered directive from June may be reshaping the pace and selection of this fortnight's KEV additions.
Occurred 14 Jul 2026
Read story →
CISA's KEV list runs a month late
CISA's risk-tiered BOD 26-04, issued 10 June, is the directive whose patching clock the FortiSandbox KEV entry starts.
Occurred 16 Jul 2026
Read story →
KEV patch clocks fell to three days
BOD 26-04's 10 June issuance is the directive whose deadline allocation this recount measures.
Occurred 28 Jul 2026
Read story →
Arista, Fortinet and Cisco flaws listed
The three new KEV entries are catalogued under BOD 26-04's risk-tiered deadline allocation.
Occurred 28 Jul 2026
Read story →
Phase II asks agencies for paperwork
Phase II is the 60-day checkpoint set by the June directive.
Occurred 9 Jun 2026
Read story →
KEV three-day deadline share fell to 71%
BOD 26-04's risk-tiered per-entry windows, replacing BOD 22-01, produced the falling three-day share observed in August's KEV additions.
Occurred 2 Sept 2026
Read story →
CISA set three-day deadlines on 34 flaws
The risk-tiered directive issued in June sets the deadline mix measured for September.
Occurred 30 Sept 2026
Read story →
Different Perspectives
Hospital Sírio-Libanês
Hospital Sírio-Libanês
Hospital Sírio-Libanês said a 21 September attack reached a reporting system for its social projects, possibly exposing patients' and staff identity numbers and health information, while its general patient database was untouched. It notified the ANPD and the Polícia Federal and warned of fraud attempts.
The Foschini Group
The Foschini Group
The Foschini Group told the Johannesburg exchange on 13 October that an attack found on 11 October disrupted IT systems at its TFG London brands, while stores stayed open. It has not identified the attackers or established whether personal data was taken.
FirstVDS
FirstVDS
FirstVDS said attackers used a VMmanager 6 flaw to copy customers' passwords, cloud credentials and cryptocurrency wallets from beneath their virtual servers, and told notified customers to assume theft and rotate credentials. ISPsystem's flaw was not fully fixed on 19 October.
ESET
ESET
ESET says Russia-aligned UAC-0099 phished a Ukrainian grain logistics firm in July 2025 and apparently passed its access to GRU-linked Sandworm, which wiped the company's data that September. It treats the attackers' use of the Yggdrasil network as a first for a state-aligned actor.
JPCERT/CC
JPCERT/CC
JPCERT/CC issued emergency alert AT-2026-0032 on 14 October as EG Secure Solutions confirmed attacks on the SiteGuard Server Edition flaw. It told operators to save diagnostic data before updating, because the update may erase traces of the attack.
Cyber Security Agency of Singapore
Cyber Security Agency of Singapore
The Cyber Security Agency of Singapore said on 20 October that attackers are exploiting Ivanti Connect Secure, seven days after Ivanti's disclosure, having flagged PAN-OS exploitation on 16 October. It issued a PHP2Shell alert on 21 October, the day the fixes shipped.

Written with AI from Lowdown's published reporting. Not individually reviewed by an editor. Editorial standards.