KEV in CVE Records: Audit of All 1,781 CISA-ADP kev Blocks

We compared every entry in CISA's KEV catalog (version 2026.11.13, 1,781 CVEs) with the CISA-ADP kev block in each CVE record, and scanned all 426,227 records in the November 17, 2026 cvelistV5 snapshot for kev blocks that point at CVEs no longer in the catalog. The record copy matches the catalog for 1,777 CVEs; this article lists the four that don't, what happens to a record when CISA removes a CVE from KEV, and a script to run the check yourself.

A wall of old wooden card-catalog drawers with brass label holders and handwritten labels, receding into the dark
Photo by Jéan Béller on Unsplash

If your vulnerability pipeline reads CVE JSON 5 records instead of the KEV catalog, you are trusting a copy. CISA’s Vulnrichment program writes a kev block into the CISA-ADP container of each CVE record that is on the Known Exploited Vulnerabilities catalog. We checked that copy against the whole catalog on November 17, 2026.

The short answer: the copy is close to complete. 1,777 of 1,781 KEV CVEs have a kev block whose dateAdded matches the catalog. Two have no block at all, two show a different date, and no record anywhere in the CVE corpus carries a kev block for a CVE that is not on the catalog, including the three CVEs CISA has removed since January 2025.

This piece goes beyond our 30-day exploitation-alert diff, which measured how quickly new KEV entries reach records. Here the question is whether the record copy can be trusted at full-catalog scale, in both directions.

Where the kev block lives

The kev block sits in the CISA-ADP container’s metrics array, next to the SSVC block that the Vulnrichment SSVC guide explains. CISA’s Vulnrichment README states the rule: “For those CVEs that are on the KEV, the CISA ADP will add a KEV block … For those that aren’t, no update will occur.”

Here is the CISA-ADP metrics content of CVE-2026-82078 (PaperCut NG/MF) as it appeared in cvelistV5 on November 17, 2026, trimmed to the two other entries:

[
  {"other": {"type": "ssvc", "content": {
    "timestamp": "2026-08-28T00:00:00+00:00",
    "options": [{"Exploitation": "active"}, {"Automatable": "no"}, {"Technical Impact": "total"}],
    "role": "CISA Coordinator", "version": "2.0.3", "id": "CVE-2026-82078"}}},
  {"other": {"type": "kev", "content": {
    "dateAdded": "2026-08-28",
    "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-82078"}}}
]

The block has two fields: dateAdded and a reference URL. Everything else KEV publishes (dueDate, requiredAction, knownRansomwareCampaignUse, notes, cwes) is only in the catalog. Our KEV JSON feed field guide covers those fields.

What we compared

InputVersion used
KEV catalogknown_exploited_vulnerabilities.json from cisagov/kev-data, catalogVersion 2026.11.13 (dateReleased 2026-11-13T20:24:18Z), 1,781 entries, dateAdded range 2021-11-03 to 2026-11-13
CVE records for KEV CVEsEach record fetched from the main branch of CVEProject/cvelistV5 on 2026-11-17 (branch head a683955)
Full CVE corpus2026-11-17_all_CVEs_at_midnight.zip.zip from the cvelistV5 release cve_2026-11-17_0000Z: 426,227 records
Removal historyGit history of known_exploited_vulnerabilities.json in cisagov/kev-data, 344 commits from 2025-01-27

Two checks ran. Forward: for every catalog CVE, does the record have a CISA-ADP kev block, and does its dateAdded equal the catalog’s? Reverse: does any record in the full corpus carry a CISA-ADP kev block for a CVE that is not in the catalog?

Results

CheckCount
KEV catalog entries1,781
Records with a CISA-ADP kev block and matching dateAdded1,777
Records with a kev block but a different dateAdded2
Records with a CISA-ADP container but no kev block2
KEV records with no CISA-ADP container0
KEV records not in PUBLISHED state0
Records in the full corpus with a kev block for a non-KEV CVE0

The 1,781 KEV CVEs span every catalog year: 311 added in 2021, 555 in 2022, 187 in 2023, 186 in 2024, 245 in 2025 and 297 so far in 2026. The kev blocks therefore cover the backfilled early catalog as well as recent additions.

Every one of the 1,781 records also carried a CISA-ADP SSVC block with Exploitation set to active, including the two without a kev block.

Two KEV CVEs with no kev block

CVECatalog entryKEV dateAddedCISA-ADP container dateUpdatedSSVC Exploitation
CVE-2026-48356Adobe Commerce and Magento2026-10-272026-10-28T03:55:44Zactive
CVE-2026-111497Google Brotli2026-10-272026-10-28T03:55:48Zactive

Both were already missing a kev block in the November 16 snapshot used in our exploitation-alert diff. Their CISA-ADP containers were updated the day after the KEV addition (the SSVC change arrived) but the kev block did not. We do not know why; CISA has not published an explanation that we could find. A pipeline that treats “kev block present” as “on KEV” would have missed both for three weeks.

Two kev blocks with a different dateAdded

CVECatalog entryCatalog dateAddedRecord kev dateAdded
CVE-2026-81578PaperCut NG/MF2026-08-312026-08-28
CVE-2026-82078PaperCut NG/MF2026-08-312026-08-28

The kev-data git history shows both CVEs first appearing in catalog version 2026.08.31, committed 2026-08-31, with dateAdded 2026-08-31, and the date never changing afterwards. The record says three days earlier, matching the timestamp on the record’s SSVC block. If you compute time-to-KEV or BOD due dates from the record, these two come out three days early. Use the catalog date; our KEV time-to-listing analysis does.

What happens to the record when a CVE leaves KEV

CISA occasionally removes entries. The kev-data history since January 27, 2025 shows three CVEs that were in the catalog and are not in it now, plus one that briefly disappeared and came back:

CVECatalog entryIn catalogRemoved from catalogRecord today
CVE-2025-4664Google Chromiumfrom version 2025.05.15version 2025.06.09no kev block; SSVC Exploitation none
CVE-2025-6264Rapid7 Velociraptorfrom version 2025.10.14version 2025.10.22no kev block; SSVC Exploitation none
CVE-2026-69836Microsoft Entra IDadded 2026-08-21 17:28 UTC commit2026-08-21 18:42 UTC commitno kev block; SSVC Exploitation none
CVE-2026-1281Ivanti EPMMadded 2026-01-29 18:15 UTC commitdropped 19:14 UTC, back 20:41 UTC the same daykev block, dateAdded 2026-01-29

These are what the data shows; the commits do not record why an entry was removed, and we did not find a CISA statement for each. The record behaviour is consistent, though: when an entry left the catalog, the record lost its kev block and its SSVC Exploitation value was set to none. A pipeline that only ever adds “exploited” flags and never clears them will keep all three marked as exploited.

The reverse scan backs this up at corpus scale: none of the 426,227 records in the November 17 snapshot carries a CISA-ADP kev block for a CVE outside the catalog.

Run the audit yourself

Tested with Python 3 on November 17, 2026. Fetch the catalog and the records, then run the script.

curl -sSO https://raw.githubusercontent.com/cisagov/kev-data/main/known_exploited_vulnerabilities.json
mkdir -p records
python3 - <<'EOF' > curl.cfg
import json
for v in json.load(open("known_exploited_vulnerabilities.json"))["vulnerabilities"]:
    cve = v["cveID"]; year, num = cve.split("-")[1:]
    path = f"cves/{year}/{int(num)//1000}xxx/{cve}.json"
    print(f'url="https://raw.githubusercontent.com/CVEProject/cvelistV5/main/{path}"')
    print(f'output="records/{cve}.json"')
EOF
curl -sS --parallel --parallel-max 16 -K curl.cfg
# audit_kev_blocks.py: compare the KEV catalog with the CISA-ADP "kev" block in each CVE record.
# Usage: python3 audit_kev_blocks.py known_exploited_vulnerabilities.json records/
import json, sys, pathlib

catalog = {v["cveID"]: v for v in json.load(open(sys.argv[1]))["vulnerabilities"]}
records = pathlib.Path(sys.argv[2])

def cisa_adp_metrics(record):
    for adp in record.get("containers", {}).get("adp", []):
        if adp.get("providerMetadata", {}).get("shortName") == "CISA-ADP":
            return {m["other"]["type"]: m["other"]["content"]
                    for m in adp.get("metrics", []) if "other" in m}
    return None

missing, date_mismatch, ok = [], [], 0
for cve, entry in sorted(catalog.items()):
    record = json.loads((records / f"{cve}.json").read_text())
    metrics = cisa_adp_metrics(record) or {}
    kev = metrics.get("kev")
    if kev is None:
        missing.append((cve, entry["dateAdded"]))
    elif kev["dateAdded"] != entry["dateAdded"]:
        date_mismatch.append((cve, entry["dateAdded"], kev["dateAdded"]))
    else:
        ok += 1

print(f"catalog entries: {len(catalog)}  matching kev block: {ok}")
print("no kev block:", missing)
print("dateAdded differs (catalog, record):", date_mismatch)

Output on November 17, 2026:

catalog entries: 1781  matching kev block: 1777
no kev block: [('CVE-2026-111497', '2026-10-27'), ('CVE-2026-48356', '2026-10-27')]
dateAdded differs (catalog, record): [('CVE-2026-81578', '2026-08-31', '2026-08-28'), ('CVE-2026-82078', '2026-08-31', '2026-08-28')]

The script assumes every catalog CVE has a published record (true on this date). For the reverse check, stream the midnight release zip with Python’s zipfile, skip any record whose bytes do not contain "kev", and collect CISA-ADP kev blocks whose CVE is not in the catalog; a full pass took about 20 seconds here. To keep the check current without refetching everything, drive it from cvelistV5 delta.json as described in our incremental CVE sync guide.

What to do with this

  1. Keep the catalog as the source of truth. It is published first, carries the fields the record lacks, and its dateAdded is the one BOD due dates are computed from.
  2. Use the kev block as a cross-check, not a trigger. Alert when the two disagree: a catalog CVE with no kev block, a kev block with a different date, or a kev block for a non-catalog CVE.
  3. Handle removals. If an exploited flag in your system came from KEV or from SSVC active, clear or re-review it when the CVE leaves the catalog or Exploitation goes back to none.
  4. Fall back to SSVC when the kev block is missing. Both missing-block CVEs had Exploitation active, so a rule of “kev block OR SSVC active OR in catalog” would not have missed them.

These steps slot into the KEV and exploitation stages of our vulnerability prioritization workflow.

Limits of this article

  • One snapshot: the catalog as of version 2026.11.13 and records as of November 17, 2026. The two missing blocks may be added later.
  • The removal history covers only what the cisagov/kev-data repository records, which starts on 2025-01-27. Earlier removals, if any, are not counted.
  • We report what the data shows about removals, not why CISA removed each entry.
  • The forward check fetched records from the moving main branch over about 11 seconds; the reverse check used the fixed midnight release.

Sources and verification

Important claimSourceStatus
1,781 catalog entries, version 2026.11.13cisagov/kev-data known_exploited_vulnerabilities.jsonVerified (computed)
1,777 matching, 2 missing, 2 date mismatchesCVEProject/cvelistV5 records, script aboveVerified (computed)
0 kev blocks for non-catalog CVEs across 426,227 recordscvelistV5 release cve_2026-11-17_0000ZVerified (computed)
CISA ADP adds a kev block only for KEV CVEscisagov/vulnrichment READMEVerified
Three removals and one remove-and-re-add since 2025-01-27cisagov/kev-data git historyVerified (computed); reasons not stated
Removed CVEs have no kev block and SSVC Exploitation nonecvelistV5 records, November 17, 2026Verified

Frequently asked questions

Does every KEV vulnerability have a kev block in its CVE record?

Almost. In our November 17, 2026 check, 1,779 of the 1,781 CVEs in KEV catalog version 2026.11.13 had a CISA-ADP kev block in their cvelistV5 record. The two exceptions, CVE-2026-48356 and CVE-2026-111497, were added to KEV on 2026-10-27 and had an SSVC Exploitation value of active but no kev block.

What happens to a CVE record when CISA removes a vulnerability from KEV?

For the three removals visible in the cisagov/kev-data history since January 2025 (CVE-2025-4664, CVE-2025-6264 and CVE-2026-69836), the current CVE records have no kev block and their CISA-ADP SSVC Exploitation value is none. A scan of all 426,227 records found no kev block for any CVE outside the catalog.

Should I use the kev block in the CVE record or the KEV catalog JSON?

Use the catalog JSON as the primary source: it is what CISA publishes first, and it carries dueDate, requiredAction and knownRansomwareCampaignUse, which the kev block does not. The kev block is useful when your pipeline already ingests CVE records, provided you reconcile it against the catalog and treat the catalog's dateAdded as authoritative.

How do I run this audit myself?

Download known_exploited_vulnerabilities.json from cisagov/kev-data, fetch each listed CVE's JSON from CVEProject/cvelistV5, and run the Python script in this article. It prints the CVEs with no kev block and those whose dateAdded differs from the catalog. On November 17, 2026 the fetch of 1,781 records took about 11 seconds with parallel curl.

Vulnerability ManagementKevCisa-AdpVulnrichmentCve Json 5Cvelistv5SsvcData Quality