Skip to content
EPSS vs CVSS

PROGRAM GUIDE, read 10 Nov 2026

BOD 26-04 sets the KEV timelines now, and BOD 22-01 is revoked

All guidesGlossary

Which directive is in force

CISA's BOD 26-04, titled Prioritizing Security Updates Based on Risk, was issued on June 10, 2026. The directive states that it supersedes and revokes BOD 19-02 and BOD 22-01. The BOD 22-01 page now carries a notice that it has been revoked and superseded by BOD 26-04.

Federal agencies work to BOD 26-04. Contracts, policies and vendor materials written before June 2026 may still cite BOD 22-01 and its two-week dates. Update those references and record the date you did.

What BOD 26-04 requires

The directive phases in. Phase I applies immediately: update vulnerability policies, monitor KEV catalog updates and continue Cyber Hygiene scanning. Phase II is due within 60 days, when agencies update vulnerability management processes based on CVE and KEV data. Phase III is due within 180 days, when agencies must meet the Table 1 remediation timelines and tag internet-reachable assets.

Table 1 uses four decision points: asset exposure, KEV status, automatable exploitation and technical impact. The remediation durations are published as an image on the directive page, so read them there and do not copy them from a secondary summary. Entries marked & forensic triage require remediation or mitigation within three days plus a forensic triage of the asset. CISA's page says Table 1 is informed by SSVC.

ItemBOD 22-01 (revoked)BOD 26-04 (current)
Timeline basisPer-entry due date in the catalog: two weeks, or six months for CVE IDs assigned before 2021Table 1: exposure, KEV status, automatable exploitation, technical impact
Fast laneNone found on 2026-11-10Entries marked & forensic triage: three days, plus forensic triage
Clock startsCatalog due dateWhen CISA adds the CVE to KEV or the agency identifies it on an asset, whichever is first
ReportingReport status of catalog vulnerabilitiesAutomated KEV status through the CDM Dashboard, or manual every two weeks if not fully automated

What the numbers mean for your queue

Under either directive the clock depends on when the CVE enters the catalog. In the KEV Lag Ledger, 318 CVEs were added between 2025-11-10 and 2026-11-09, about 6 per week, and the monthly count ranged from 17 to 43 across full months. A program that reviews KEV weekly will see its backlog change weekly.

Because 17.3% of additions were published more than a year before listing, a share of the CVEs that start a clock are old. They are in your asset data already. Match each new addition against the whole inventory the day it appears, not against new scan results only.

Build the process, not the date

BOD 26-04 states that timelines change as facts change. Removing an asset from the internet changes its exposure value and can lengthen its timeline. Keep the exposure tag on each asset current and dated, since it now decides the deadline. The directive asks agencies to report asset tags covering organization, environment, exposure and asset type.

Record, per KEV entry, the date CISA listed it, the date you matched it to an asset, the timeline applied, the date of closure and the evidence. Those five fields answer most audit questions on a KEV deadline. Keep them in one table keyed by CVE ID and asset, so that a single filter returns every open item past its timeline.

  • Pull the KEV feed at least daily and diff it against yesterday's copy.
  • Match by CVE ID against every asset, including those scanned less often.
  • Tag internet-reachable assets and date the tag.
  • Non-federal organizations: state in your policy whether you adopt the directive's timelines by reference.

Where BOD 22-01 still appears

Older runbooks, audit findings and vendor datasheets may still describe the two-week rule. Treat those as historical. When an auditor quotes the old dates, answer with the current directive and its issue date, and show the change record.

The catalog itself continues. CISA's FAQ criteria for adding an entry (a CVE ID, clear remediation guidance and reliable evidence of exploitation in the wild) were stated in the BOD 22-01 materials, and the KEV feed is still the input your tooling reads. Its release on 2026-11-09 was catalog version 2026.11.09, which is the version the ledger was built from. Record the catalog version beside every KEV match you report, so the match can be rerun against the same file.

Sources

  1. CISA, BOD 22-01 (revoked), read 10 Nov 2026
  2. CISA, BOD 26-04: Prioritizing Security Updates Based on Risk, read 10 Nov 2026

Last reviewed 10 Nov 2026.