CISA ties federal patch deadlines to four yes-or-no questions about each CVE
BOD 26-04 makes remediation urgency a function of exposure, KEV status, exploit automation and technical impact. CISA publishes three of those four answers per CVE; agencies determine the fourth themselves.
The Watch · Security desk

What happened
- CISA issued Binding Operational Directive 26-04, Prioritizing Security Updates Based on Risk, a compulsory direction that federal agencies are required to comply with under 44 U.S.C. 3554(a)(1)(B)(ii).
- Remediation urgency is set by four variables, asset exposure, KEV status, exploit automation and technical impact, with the intervals attached to each combination held in the directive's Table 1.
- The directive extends the KEV catalog model established under BOD 22-01 by keeping timely action on high-risk vulnerabilities and deferring action against low-risk ones.
Why it matters
- What it limits constraint With deferral written into a compulsory directive, the internal fight inside a federal vulnerability program stops being whether everything gets patched and becomes whether the risk call on each asset can be defended.
- Who's exposed exposure Asset exposure is the one input the agency decides for itself, so a stale inventory quietly places an internet-facing box on a slower clock and no CISA feed will correct it.
- What's now possible capability Because the three CISA-supplied answers are published per CVE ID, a private program can adopt the same tiering logic and defend it as federal practice while carrying none of the directive's obligations.
Next story · Security · yesterday
CISA gives agencies until October 17 to fix four exploited bugs in Cisco, Palo Alto and Ahsay productsConfirmed3 publishers
Four questions with two answers each produce sixteen possible risk profiles [13], and CISA answers three of the four before an agency looks at anything. KEV status, exploit automation and technical impact are published per CVE ID through services including the Vulnrichment Program [10]. The remaining variable, whether the vulnerable asset is publicly exposed, is the agency's own determination, made against CISA's Internet Exposure Reduction Guidance [11]. One of the four inputs is owned locally [14].
Enrichment data cannot know what an agency has facing the public internet. An inventory that records an internet-facing appliance as internal moves every CVE on that appliance into a slower tier, and the mistake is invisible in the CVE feed, because the feed is correct and the asset record is not.
BOD 22-01 in 2021 pointed agencies at the Known Exploited Vulnerabilities catalog and told them to remediate aggressively [2]. 26-04 keeps that urgency for high-risk items and adds deferral of low-risk ones [3], with CISA describing the approach as focusing effort on the areas of highest risk rather than treating all vulnerabilities and systems equally [4]. A program that formally deprioritizes a CVE now does so with a compulsory directive behind it.
BOD 26-04 binds Federal Civilian Executive Branch agencies [7] and does not apply to statutorily defined national security systems or to certain systems operated by the Department of War or the Intelligence Community [8]. Nothing in it obliges a vendor, a contractor or a private enterprise. What crosses that boundary is the data: any organization can pull the same three published answers per CVE [10] and run the same tiering, without any obligation to do so.
CISA's stated reason for changing the model is that threat actors exploit unpatched vulnerabilities, and that their use of AI may further narrow the time defenders have between patch release and possible exploitation [5]. CISA frames that as a possibility rather than a confirmed measurement. The directive is aligned to OMB Circular A-130 and FISMA, and CISA has issued separate implementation guidance for agencies working through it [12].
For federal teams the deadline now comes out of four fields, three delivered by CISA and one produced by whatever the asset inventory says [14]. Inventory accuracy has become a scheduling control.
What to watch
- Whether the Table 1 intervals for the top risk tier come in shorter than the KEV deadlines agencies have worked to since BOD 22-01.
- Whether Vulnrichment coverage keeps pace with CVE publication volume, since three of the four deadline inputs come from it.
- Whether agencies must report their asset exposure determinations to CISA or keep them internal, which decides whether the deferral half is auditable.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence80
- Adoption
- Not scored
- Hype gap+10
- Incentives50
- Confidence72
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
CISA issued Binding Operational Directive 26-04, "Prioritizing Security Updates Based on Risk".
- [2]
In 2021 CISA established the Known Exploited Vulnerabilities catalog pursuant to BOD 22-01, which directed agencies to aggressively remediate known exploited vulnerabilities.
- [3]
The directive evolves upon CISA's KEV Catalog by prioritizing high-risk vulnerabilities for timely action while deferring action against low-risk vulnerabilities.
- [4]
CISA describes the approach as focusing patching efforts on the areas of highest risk rather than treating all vulnerabilities and systems equally.
- [5]
CISA states that cyber threat actors exploit unpatched vulnerabilities and that their use of AI may further narrow the time defenders have to react between patch release and possible exploitation.
- [6]
A Binding Operational Directive is a compulsory direction to federal executive branch departments and agencies for safeguarding federal information and information systems under 44 U.S.C. 3552(b)(1); federal agencies are required to comply under 44 U.S.C. 3554(a)(1)(B)(ii).
- [7]
The directive refers to the systems to which it applies as Federal Civilian Executive Branch systems, and to the agencies operating them as Federal Civilian Executive Branch agencies.
- [8]
These directives do not apply to statutorily defined national security systems or to certain systems operated by the Department of War or the Intelligence Community.
- [9]
The urgency of remediation, per the directive's Table 1: Remediation Timelines, is determined by four variables: asset exposure (is the vulnerable asset publicly exposed), KEV status (is the CVE ID on CISA's Known Exploited Vulnerabilities Catalog), exploit automation (can an adversary automate all the steps necessary to exploit), and technical impact (does an adversary gain partial or total control of the asset after exploitation).
- [10]
CISA publishes answers to KEV Status, Exploit Automation, and Technical Impact for every CVE ID through services such as the Vulnrichment Program.
- [11]
Agencies should follow CISA's Internet Exposure Reduction Guidance to answer Asset Exposure and determine whether the vulnerable asset is publicly exposed.
- [12]
The directive's requirements align with OMB Circular A-130 and the Federal Information Security Modernization Act of 2014, and CISA developed Implementation Guidance: Prioritizing Security Updates Based on Risk to support agencies.
- [13]
The four variables as posed each admit two answers, producing 16 distinct risk profiles.
- [14]
Of the four variables that set remediation urgency, CISA publishes three per CVE ID and agencies determine the remaining one, asset exposure, themselves.
Sources
2 independent publishers whose own reporting we read for this story.
- cisa.govBOD 26-04: Prioritizing Security Updates Based on Risk | CISA
1 article · September 6, 2026
- cyberscoop.comWhy federal cyber defense demands an offense-driven mindset
1 article · September 8, 2026
Topics and entities
Entities
- Federal Information Security Modernization Act of 2014
- Vulnrichment Program
- CISA Known Exploited Vulnerabilities Catalog
- Binding Operational Directive 26-04
- CISA
- BOD 22-01