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
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.
Publicly exposed?: Yes or No
On the KEV catalog?: No or Yes
Yes · No
Publicly exposed?: Yes. On the KEV catalog?: No.
3, 14 or 60 days
- Three days only if automatable with total control
Yes · Yes
Publicly exposed?: Yes. On the KEV catalog?: Yes.
3 to 14 days
- Triage joins the 3 days on total control
No · No
Publicly exposed?: No. On the KEV catalog?: No.
60 days or the next upgrade
- Upgrade when not automatable
No · Yes
Publicly exposed?: No. On the KEV catalog?: 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 impact | Timeline |
|---|---|---|---|---|
| Yes | Yes | Yes | Total control | 3 days and forensic triage |
| Yes | Yes | Yes | Partial control | 3 days |
| Yes | Yes | No | Total control | 3 days and forensic triage |
| Yes | Yes | No | Partial control | 14 days |
| Yes | No | Yes | Total control | 3 days |
| Yes | No | Yes | Partial control | 14 days |
| Yes | No | No | Total control | 14 days |
| Yes | No | No | Partial control | 60 days |
| No | Yes | Yes | Total control | 3 days and forensic triage |
| No | Yes | Yes | Partial control | 14 days |
| No | Yes | No | Total control | 14 days |
| No | Yes | No | Partial control | 14 days |
| No | No | Yes | Total control | 60 days |
| No | No | Yes | Partial control | 60 days |
| No | No | No | Total control | Fix on system upgrade |
| No | No | No | Partial control | Fix on system upgrade |
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.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.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.Look up the table row for each item and set its due date.
Sources
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.
- Phone
- (214) 723-2510
- 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.
$199/month
Billed monthly
$182.42/month
Billed yearly
$499/month
Billed monthly
$457.42/month
Billed yearly
- Scammers stopped from sending email as you
- Your website and systems scanned every week
- Your email settings checked every week
- Everything in the 1 to 10 plan
- Covers up to 50 people
$199/month
after a one-time setup fee
- A site planned, designed and built for you
- Hosting and updates every month
$499/month
Billed monthly
$457.42/month
Billed yearly
$999/month
Billed monthly
$915.75/month
Billed yearly
- Your Google profile, fully set up
- A Google post every week
- 2 social posts a week
- Everything in Get found
- 4 social posts a week
- Your top 10 Google searches tracked
from$500/month
after a one-time setup fee
- Your data gathered from the tools you use
- A first analysis that answers your questions
- New findings every month
Related reading
Security4 min readVulnerability research: most of the work is ruling things out
A recon pass hands you hundreds of finding-shaped candidates. Which ones die is a person's call; two gates around that call are mechanical.
Engineering4 min readForensic readiness: the logging you need before a breach
Retention, endpoint telemetry and audit trails are decided months before an incident, and they set what an investigation can ever establish.
Security3 min readPenetration test vs vulnerability scan: what you are actually buying
Both are legitimate purchases. A sample report and a look for chaining show which one a quote is selling, and four questions test the vendor behind it.
