Skip to content

Security

Vulnerability prioritization: you do not have 4,000 critical CVEs

A CVSS-sorted export doesn't say what to fix first. CISA's June 2026 directive shows what to sort by instead, and a manufacturer or clinic can borrow it.

Computing America Cyber. Security assessments, penetration testing and staff training.

Send the export
4 min readComputing America
Hundreds of blank red tags on a wall board, one pulled out and clipped apart from the rest.

In short

  • A severity score says what a flaw does if it works. A deadline also needs to know whether anyone is exploiting it and whether the affected system is reachable from the internet.
  • CISA's KEV catalog lists vulnerabilities observed being exploited in the wild, 1,699 of them through September 8, 2026. The set is small enough to join against a scanner export mechanically, and it's where remediation starts.
  • BOD 26-04, issued June 10, 2026, superseded BOD 22-01 and replaced per-entry KEV due dates with timelines from three days to "fix on system upgrade."
  • Four questions set the timeline: asset exposure, KEV status, exploit automation and technical impact. The directive says CISA publishes the last three for every CVE ID, so asset exposure is the one answer only you can supply.
  • In the directive's table, any KEV-listed vulnerability is due in three or 14 days, exposed or not. One that is unexposed, unlisted and not automatable waits for the next system upgrade.

Most of a backlog of four thousand distinct critical CVEs will not be on the KEV catalog. BOD 26-04 gives a way to sort the rest: four questions and a 16-row timeline table, complete enough to run on your own scanner export.

Sorting by CVSS gives you a number and no answer to which findings get fixed this month. A CVSS base score doesn't say whether anyone is exploiting a flaw or whether the affected system is reachable from the internet. In June 2026 CISA changed its own method to ask both, in public, with its reasoning attached.

What the federal government does now

BOD 22-01 (opens in a new tab) required federal civilian agencies to "remediate each vulnerability according to the timelines set forth" in the Known Exploited Vulnerabilities catalog (opens in a new tab). Each entry carried its own due date: two weeks by default, six months for a CVE ID assigned before 2021, and CISA could adjust either. The catalog is the useful half: only vulnerabilities observed being exploited in the wild. It held 1,699 entries through September 8, 2026, and four more were added on September 9. That figure moves, so treat it as a dated reading.

On June 10, 2026, Binding Operational Directive 26-04 superseded BOD 22-01 (opens in a new tab) and BOD 19-02. It kept the catalog and sets the deadline from four answers instead of a date on the entry. The table runs from three days to "fix on system upgrade." Three rows add a forensic triage of the asset to the three-day deadline, so the directive asks whether you were late as well as whether you've patched.

Fig. 1

Publicly exposed?: Yes or No

On the KEV catalog?: No or Yes

Yes · No

3, 14 or 60 days

  • Three days only if automatable with total control

Yes · Yes

3 to 14 days

  • Triage joins the 3 days on total control

No · No

60 days or the next upgrade

  • Upgrade when not automatable

No · Yes

3 to 14 days

  • Triage on automatable, total control

Only a CVE that is neither exposed nor in KEV can wait for the next system upgrade, and only if it is not automatable; every other quadrant is due within 60 days.

SourceCISA, BOD 26-04, issued June 10, 2026. Each quadrant summarizes four rows of Table 1, which this article reproduces in full; automatable and technical impact set the day within it.

The table that sets the deadline

CISA says the table is informed by SSVC, the Stakeholder-Specific Vulnerability Categorization (opens in a new tab), a vulnerability-analysis methodology developed with Carnegie Mellon's Software Engineering Institute. Technical impact is the factor closest to a CVSS score: the directive calls it "similar to" the CVSS base score's concept of severity. Timelines are calendar days.

Exposed?In KEV?Automatable?Technical impactTimeline
YesYesYesTotal control3 days and forensic triage
YesYesYesPartial control3 days
YesYesNoTotal control3 days and forensic triage
YesYesNoPartial control14 days
YesNoYesTotal control3 days
YesNoYesPartial control14 days
YesNoNoTotal control14 days
YesNoNoPartial control60 days
NoYesYesTotal control3 days and forensic triage
NoYesYesPartial control14 days
NoYesNoTotal control14 days
NoYesNoPartial control14 days
NoNoYesTotal control60 days
NoNoYesPartial control60 days
NoNoNoTotal controlFix on system upgrade
NoNoNoPartial controlFix on system upgrade
BOD 26-04, Table 1: remediation timelines in calendar days, all 16 rows.

A ranked list cuts wherever this month's capacity runs out. When a director asks why item 900 wasn't fixed, "we got to 400" stops being the answer. A table row gives a reason someone can defend or overrule: it isn't exposed, isn't in KEV, can't be automated and yields partial control, so it waits for the next upgrade.

Borrowing it when you are not a federal agency

The directive binds federal civilian agencies, not a manufacturer or a clinic, so adopting its timelines is a choice. The inputs are within reach. Your exposure is the one input you supply. The directive counts an asset as exposed if unauthenticated or untrusted parties can reach it over a public network, wherever it physically sits, and tells agencies to follow CISA's Internet Exposure Reduction Guidance (opens in a new tab).

Get the answer from an external scan of your public IP ranges and domains, plus your firewall and NAT rules for internal hosts published through them, and key it to the scanner's asset ID. If any method finds an asset exposed, the directive says to answer Yes. For the other three inputs, the directive states that CISA publishes answers to KEV Status, Exploit Automation, and Technical Impact for every CVE ID through services such as the Vulnrichment Program (opens in a new tab).

Two limits apply. This prioritizes the backlog and leaves its size alone: a flaw in a fix-on-upgrade row is still a flaw, and a program that doesn't work those rows has only moved its backlog. And KEV records observed exploitation, so absence from it is weak evidence and no clean bill of health. The exposure and automatable columns partly cover that gap.

Re-rank your backlog this week

  1. 1.Export the scanner results and join them against the KEV catalog, which CISA publishes as known_exploited_vulnerabilities.csv (opens in a new tab). For a four-thousand-row export, script the join on the CVE ID in the file's cveID column.
  2. 2.For each CVE ID, copy the automatable and technical-impact values from the SSVC fields in its CISA record, which the cisagov/vulnrichment (opens in a new tab) repository carries, one file per CVE at a path like 2024/25xxx/CVE-2024-25522.json. In each file the options array holds Exploitation, Automatable and Technical Impact. If a CVE has no Vulnrichment record, treat it as automatable and total control until you've read it. Then add the exposure answer for the asset.
  3. 3.Look up the table row for each item and set its due date.

Sources

  1. 1.Known Exploited Vulnerabilities Catalog (opens in a new tab), CISA
  2. 2.Binding Operational Directive 26-04: Prioritizing Security Updates Based on Risk (opens in a new tab), CISA,
  3. 3.Stakeholder-Specific Vulnerability Categorization (SSVC) (opens in a new tab), CISA

Next step

Send us the scanner export.

We will re-rank it against the KEV catalog and the four BOD 26-04 factors and send back the short list, with the reasoning for each row so you can argue with it.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing