# Known-exploited lists: what they prove and what they miss

Method, read 19 Nov 2026

**The short answer.** The CISA Known Exploited Vulnerabilities catalog lists CVEs with reliable evidence of active exploitation and a clear fix. Release 2026.11.18 holds 1,786 entries, and 33 of the 37 ledger CVEs are in it. A listing shows the flaw was exploited somewhere, not on your systems, and its dateAdded is the latest date exploitation can have started.

CISA's Binding Operational Directive 22-01 says: "CISA will determine vulnerabilities warranting inclusion in the catalog based on reliable evidence that the exploit is being actively used to exploit public or private organizations by a threat actor." The catalog page lists three thresholds: an assigned CVE ID, "reliable evidence that the vulnerability has been actively exploited in the wild," and "a clear remediation action for the vulnerability, such as a vendor-provided update." The directive binds federal executive civilian agencies, who must remediate within a timeframe CISA sets. CISA's FAQ adds two cautions: "a vulnerability's exploitability is not considered as criteria for inclusion in the KEV catalog," and "we do not recommend exclusive use of the KEV Catalog as the only criterion on which organizations triage vulnerabilities." The catalog page says BOD 26-04, issued on 10 Jun 2026, carries these criteria forward.

In practice a team downloads the JSON or CSV feed on a schedule and joins its cveID field to the CVE IDs in its scanner and asset inventory. Each entry carries dateAdded, dueDate, knownRansomwareCampaignUse and forensicTriage. BOD 26-04 defines the forensic-triage marker: remediation or mitigation within three days, and "carry out a forensic triage of the asset to assess whether the system is compromised." The release read on 19 Nov 2026 is version 2026.11.18, dated 18 Nov 2026 and holding 1,786 entries. New entries trigger a check for affected assets, and the dueDate gives the team a reference date for its own deadline.

Two ledger entries show the range. CVE-2026-102764 is an origin-validation flaw in BeyondTrust Remote Support, rated 9.3 (CVSS 4.0 base score). BeyondTrust and Mandiant place the first exploitation at 29 Aug 2026, 47 days before disclosure on 15 Oct 2026. CISA listed it on 16 Oct 2026 with a due date of 19 Oct 2026. A team that waited for the catalog learned of it 48 days after the first attack. CVE-2026-41709, the ESX flaw rated 2.7 (CVSS base score), was listed on 28 Oct 2026 with a due date of 11 Nov 2026, 14 days out. Across the 33 ledger CVEs in the feed, 22 carry a 3-day window and 11 a 14-day window, and forensicTriage reads Yes on 19 of the 22 three-day entries and on none of the 14-day entries.

The list gives the wrong answer in these cases. Absence is not safety: four ledger CVEs are absent from the 18 Nov feed, listed in the table below. Listing can lag exploitation by months: SOCRadar places exploitation of Apache Tomcat CVE-2026-34486 at about 24 to 29 Apr 2026, and CISA listed it on 4 Aug 2026, about 102 days after the start of that range. A listing says a flaw is exploited somewhere, so a listed flaw in a product you run only on an isolated segment still needs a reachability check. The KEV added and due dates for all 37 ledger CVEs are in the [ledger dataset](/datasets/).

## The four ledger CVEs not in the catalog

| CVE | Product | Disclosed | CVSS base | EPSS (18 Nov 2026) | Dated exploitation in the ledger |
| --- | --- | --- | --- | --- | --- |
| CVE-2026-16723 | fastjson 1.x | 21 Jul 2026 | 9.0 | 0.00663 | None |
| CVE-2026-75604 | Next.js on Windows | 25 Aug 2026 | 9.0 | 0.02105 | None |
| CVE-2026-80521 | Linux AF_UNIX garbage collector | 26 Aug 2026 | 7.8 | 0.00178 | None |
| CVE-2026-94545 | Satori and Next.js next/og | 30 Sep 2026 | 5.3 | 0.01082 | None |

Status in release 2026.11.18 of the CISA feed. Absence from the catalog means CISA holds no listing for the CVE; it does not say that the flaw is safe to leave. CVE-2026-94545 is dated by its advisory publication on 30 Sep 2026; the Next.js 16.3.6 release that carries the fix came on 22 Sep 2026.

## A worked join on release 2026.11.18

The inventory is constructed; the output below is copied unchanged from the feed, release 2026.11.18 downloaded on 19 Nov 2026, where dates are written YYYY-MM-DD. inventory.csv has the columns host and cve and five rows: mail-gw-01 with CVE-2026-104286, fw-edge-02 with CVE-2026-0322, esx-lab-03 with CVE-2026-41709, orders-api with CVE-2026-16723 and tomcat-04 with CVE-2026-34486. The command pulls the four fields a team needs for each match:

```
jq -r --rawfile inv inventory.csv '($inv | gsub("\r";"") | split("\n")[1:] | map(select(length>0) | split(",")[1])) as $ids | .vulnerabilities[] | select(.cveID as $c | $ids | index($c)) | [.cveID, .dateAdded, .dueDate, .knownRansomwareCampaignUse, .forensicTriage] | @csv' known_exploited_vulnerabilities.json | sort
```

It printed:

```
"CVE-2026-0322","2026-10-14","2026-10-17","Unknown","Yes"
"CVE-2026-104286","2026-10-01","2026-10-04","Unknown","Yes"
"CVE-2026-34486","2026-08-04","2026-08-07","Unknown","No"
"CVE-2026-41709","2026-10-28","2026-11-11","Unknown","No"
```

Four of the five hosts match. CVE-2026-16723 on orders-api returns no line because it is not in the feed, so the ticket records it as not listed, which says nothing about exposure (see the table above). The windows differ: mail-gw-01 (1 Oct to 4 Oct) and fw-edge-02 (14 Oct to 17 Oct) have 3 days and forensicTriage Yes, so each needs the patch and a compromise check by the due date. tomcat-04 (4 Aug to 7 Aug) also has 3 days but forensicTriage No, so it needs the patch only. esx-lab-03 (28 Oct to 11 Nov) has 14 days and No. All four report knownRansomwareCampaignUse as Unknown, which is not a statement that no ransomware actor uses the flaw.

## Steps, owners and how they fail

- Vulnerability analyst: downloads the JSON feed on a schedule, joins cveID to the CVE IDs in the scanner and the asset inventory, and lists new entries. Record: the catalogVersion read, and for each match the dateAdded and dueDate.
- Asset owner: confirms whether the matched product and version are in use and where. Record: the affected asset list in the ticket.
- Vulnerability manager: sets the internal deadline, which is the dueDate or an earlier date the organization chooses. Record: the deadline and who agreed it.
- Failure: a stale copy. Compare the catalogVersion with the current release before each report, and do not report from a copy older than the last listing.
- Failure: inventory gaps. A listed CVE that matches no asset is recorded as unmatched, not as not affected, until the inventory is shown to cover the product.
- Failure: names that do not match. The feed gives vendorProject and product as text, so a product known to the inventory under another name is missed unless the join also uses the CVE ID.

## Ledger entries it settles

- [CVE-2026-41709: Broadcom VMware ESX](/ledger/cve-2026-41709/): disclosed 29 Jul 2026
- [CVE-2026-75650: Adobe Commerce and Magento Open Source](/ledger/cve-2026-75650/): disclosed 7 Sep 2026

## Related pages

- [Runtime reachability and live-state reads: what they prove and what they miss](/methods/runtime-reachability/)
- [EPSS exploit prediction: what it proves and what it misses](/methods/exploit-prediction/)
- [Severity scores: what they prove and what they miss](/methods/severity-score/)

## Sources

- CISA BOD 22-01: https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities (read 19 Nov 2026)
- CISA KEV catalog page: three criteria and FAQ: https://www.cisa.gov/known-exploited-vulnerabilities (read 19 Nov 2026)
- CISA KEV JSON feed, version 2026.11.18: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)
- BeyondTrust blog on BT26-05 (CVE-2026-102764): https://www.beyondtrust.com/blog/entry/bt26-05 (read 19 Nov 2026)
- Broadcom advisory for CVE-2026-41709: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 (read 10 Nov 2026)
- CISA kev-data README: update schedule: https://raw.githubusercontent.com/cisagov/kev-data/develop/README.md (read 10 Nov 2026)
- SOCRadar report on the SNOWLIGHT campaign (CVE-2026-34486): https://socradar.io/blog/snowlight-government-chinese-campaign/ (read 19 Nov 2026)
- CISA BOD 26-04: Prioritizing Security Updates Based on Risk: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/methods/known-exploited/
