From 2023 through 2025, nearly every entry in the CISA known exploited vulnerabilities catalog came with a 21-day due date. Of the 139 entries added between June 11 and October 23, 2026, 113 came with three days. The change is Binding Operational Directive (BOD) 26-04, and it moves part of the deadline calculation from CISA to each agency's own asset data.
What is the CISA known exploited vulnerabilities catalog?
The KEV catalog is the Cybersecurity and Infrastructure Security Agency's (CISA) public list of vulnerabilities that attackers are known to be using. Under the criteria CISA published with BOD 22-01, an entry needs a CVE ID, "clear remediation guidance" and "reliable evidence of exploitation in the wild."
Catalog version 2026.10.23 holds 1,756 entries, and 361 of them are marked as known to be used in ransomware campaigns. CISA publishes the catalog as a web page and as a JSON data feed. The feed is what scanners and ticketing systems should pull, since it carries every field and a version number you can log.
What were KEV due dates before BOD 26-04?
BOD 22-01 told agencies to remediate "according to the timelines set forth in the CISA-managed vulnerability catalog." It set defaults of "two weeks" for CVEs assigned in 2021 or later and "6 months" for older ones, which "may be adjusted in the case of grave risk to the Federal Enterprise."
Many explainers stop at those defaults. The catalog's own data shows what CISA actually assigned:
| Year added | Entries | Most common due date |
|---|---|---|
| 2021 | 311 | 181 days (189 entries) and 14 days (111) |
| 2022 | 555 | 21 days (403 entries) |
| 2023 | 187 | 21 days (177 entries) |
| 2024 | 186 | 21 days (175 entries) |
| 2025 | 245 | 21 days (226 entries) |
Older CVEs got the same treatment after the first year: of the 506 pre-2021 CVEs added from 2022 until June 9, 2026, 384 had 21 days. For most federal teams, three weeks was the working norm.
What changed with BOD 26-04?
CISA issued BOD 26-04, "Prioritizing Security Updates Based on Risk," on June 10, 2026. Its announcement describes the directive as "harmonizing and improving" BOD 19-02 and BOD 22-01. Instead of one clock per vulnerability, the timeline depends on four factors for each affected asset: whether it is publicly exposed, whether the vulnerability is in the KEV catalog, whether exploitation can be automated, and whether it gives an attacker partial or total control.
Coverage of the directive agrees on the outline. The highest-risk combinations get three calendar days. Many other KEVs get 14 days. Lower-risk combinations get 60 days, and the lowest-risk cases can wait for the system's next scheduled upgrade. Published summaries tie the forensic triage requirement to KEVs that give an attacker total control. The implementation guidance maps every combination in a table; use that table, not a summary (including this one), when you encode the rules in tooling.
CISA expects few instances at the top. In an initial analysis at one large civilian agency, it found about 1% of vulnerability instances fell into the three-day category and more than 60% could be deferred to the next upgrade, as Nextgov/FCW and The Record reported.
How do you read a KEV entry now?
We counted the entries added since BOD 26-04 in the catalog's JSON feed:
| Entries added June 11 to October 23, 2026 | Count |
|---|---|
| Three-day due date, forensicTriage "Yes" | 91 |
| Three-day due date, forensicTriage "No" | 22 |
| 14-day due date, forensicTriage "No" | 26 |
| Total (all cite BOD 26-04) | 139 |
The 1% figure and this table measure different things. The 1% counts vulnerabilities on individual assets at one agency, most of which never reach the catalog. The table counts CVEs that CISA has already confirmed are being exploited, and most of those land in the top tier.
Three fields carry the meaning. The dueDate is the date CISA lists for the entry. The forensicTriage field says whether CISA expects a compromise check; every entry before June 11 reads "No." The requiredAction text is identical on all 139 new entries, whether or not triage is flagged, so read the field, not the text. That text also says: "Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines."
CISA supplies the KEV, automatability and technical impact answers through its Vulnrichment program, according to the Cloud Security Alliance's analysis. Exposure is the agency's call. The sources we reviewed don't say whether the catalog's due date assumes the worst-case exposure, so check your own exposure answer against the guidance's table rather than relying on the catalog date alone.
The days are calendar days. Of the 113 three-day due dates in the window, 46 fell on a Saturday or Sunday. The October 23, 2026 listing of CVE-2026-114625, a SQL injection flaw in Arista VeloCloud Orchestrator, is a typical example: added on a Friday, due Monday, triage flagged.
Who has to meet the KEV deadlines?
BOD 26-04 applies to federal civilian executive branch agency information systems and does not bind contractors directly. According to the Wiley law firm's analysis, agencies are directed to "review contracts to ensure that contractors who support or operate agency information systems" can help ensure compliance. If you operate a system for an agency, your obligation comes through your contract. Read its vulnerability clauses and ask the contracting officer whether a modification is coming, rather than guessing which timelines will flow down.
Cloud services have a parallel track. FedRAMP's notice NTC-0014 makes its Vulnerability Detection and Response (VDR) and Vulnerability Evaluation and Reporting (VER) rules mandatory on December 7, 2026 for all offerings obtaining or maintaining FedRAMP Certification. Its VDR-TFR-KEV requirement says KEVs must be remediated on BOD 26-04 timelines unless there are valid technical reasons not to. FedRAMP also says the legacy monthly vulnerability scanning most Rev5 certified services use is not enough. Offerings not yet following the rules can keep certification under a corrective action plan, with notice to all agencies, until March 7, 2027; after that, FedRAMP says certification "will be revoked." Our FedRAMP 20x explainer covers how those rules fit the rest of the program.
What should agencies do before December 7?
FedRAMP's notice lists August 7, 2026 as the date for agency policies that support ongoing remediation and December 7, 2026 for agencies to begin remediating on BOD 26-04 timelines. CISA's announcement also asks agencies to identify and tag agency-managed and publicly exposed assets, keep CISA's Cyber Hygiene scanning in place and attest quarterly to their exposed IP addresses and domain names.
Start with the exposure data, since it is the input CISA leaves to you. An inventory that marks which systems face the internet is what turns a KEV listing into a deadline; without it, every listing has to be treated as worst case. Then pull the JSON feed on a schedule, match cveID against scanner findings and open tickets that carry CISA's due date, the triage flag and your exposure answer. Log the catalog version on each ticket so an auditor can see what you knew and when.
Write the forensic triage procedure before you need it: who checks for compromise, what evidence they look at and how they record the result inside a three-day window that may include a weekend. Our cybersecurity teams support agencies with FISMA, NIST and FedRAMP compliance work.
From our delivery teams: Run a tabletop on a Friday KEV listing before December 7. It shows quickly whether anyone knows which servers are internet-facing and who is on call to do the triage.
The Bottom Line
The KEV catalog still tells you what attackers are using, but under BOD 26-04 the deadline for a given system also depends on exposure data that CISA leaves to each agency. Get exposure tagged and a forensic triage procedure written before December 7, so a three-day listing starts a known process instead of a meeting.
FAQ
What is the CISA KEV catalog?
It is CISA's public list of vulnerabilities known to be exploited in the wild. Under the criteria CISA published with BOD 22-01, an entry needs a CVE ID, clear remediation guidance and reliable evidence of exploitation. Each entry lists the product, a required action, a due date, ransomware use and, now, a forensic triage flag.
How long do federal agencies have to fix a KEV vulnerability?
Under BOD 26-04 it depends on the asset as well as the vulnerability. The highest-risk combinations get three calendar days, and many other KEVs get 14 days. The implementation guidance maps every combination of the four risk factors, and agencies must meet the new timelines by December 7, 2026.
Is BOD 22-01 still in effect?
Published analyses, including the Cloud Security Alliance's, say BOD 26-04 supersedes BOD 22-01 and BOD 19-02; CISA's own announcement calls it "harmonizing and improving" both. The KEV catalog continues, and every entry added since June 11, 2026 cites BOD 26-04 rather than BOD 22-01.
Do contractors have to follow the KEV deadlines?
BOD 26-04 binds federal civilian executive branch agencies, not contractors directly. Agencies are directed to review contracts so contractors that support or operate agency systems can help ensure compliance, so what you must do comes from your contract, as your contracting officer reads it. FedRAMP cloud services have their own KEV remediation rule.
What does forensic triage mean in a KEV entry?
It means checking whether a system was already compromised, because, as CISA put it, applying a patch generally does not evict a threat actor. In the catalog, the forensicTriage field is what tells you whether it applies; the required action text is the same on every new entry.
Sources
- CISA, Known Exploited Vulnerabilities Catalog, JSON data feed (catalog version 2026.10.23)
- CISA, BOD 22-01, Reducing the Significant Risk of Known Exploited Vulnerabilities
- CISA, CISA Releases Binding Operational Directive 26-04 on Prioritizing Security Updates Based on Risk (June 10, 2026)
- FedRAMP, NTC-0014, FedRAMP Response to CISA BOD 26-04 (June 16, 2026)
- Nextgov/FCW, CISA directive revamps how agencies prioritize vulnerable systems (June 10, 2026)
- The Record, CISA to require federal agencies to patch some cyber vulnerabilities within 3 days (June 10, 2026)
- Cloud Security Alliance, CISA's BOD 26-04, A Risk-Based Reset of Patch Rules
- Wiley, CISA Directive Highlights Risk-Based Vulnerability Management (June 10, 2026)
How we researched this. Every number, date and requirement here is checked against the sources listed above, primary documents first, and the post is fact-checked again before publication. When a rule, date or status changes, we update the post and log the change below. Read our editorial standards or send a correction.





