CVE Exploitation Alerts: Diff CISA-ADP KEV and SSVC Data

A CVE record's CISA-ADP container gains a KEV block and an SSVC Exploitation value of active when exploitation is confirmed. We diffed 31,312 changed records between the October 17 and November 16, 2026 cvelistV5 snapshots to see how those signals move, then built a small watcher that alerts on them.

A person standing on a frozen, rocky shore holds a lit flare above their head, trailing a cloud of red smoke against a white sky
Photo by Hugo Jehanne on Unsplash

If you want to know the moment a CVE in your inventory becomes exploited, there are two machine-readable places to look: CISA’s KEV JSON feed and the CISA-ADP container inside the CVE record itself. The record carries an SSVC Exploitation value (none, poc or active) and, for KEV CVEs, a kev block. Diffing those two fields between record versions gives you an exploitation alert that rides on the same cvelistV5 sync you may already run.

We measured how those fields actually moved over 30 days, from the cvelistV5 snapshot tagged cve_2026-10-17_0000Z to cve_2026-11-16_0000Z. The short answer: in this window, active never appeared on a CVE that was not already in KEV, and the kev block followed the KEV catalog by about a day, with two misses. So the KEV feed stays the primary trigger; the CVE-record diff is the second signal, and it is the one that catches poc changes and rejections.

This builds on the vulnerability prioritization workflow, where exploitation is the first gate on the way from CVE record to ticket.

Where the exploitation signals live in a CVE record

CISA publishes its enrichment through an Authorized Data Publisher container (see CVE ADP containers for how ADP containers relate to the CNA’s). In a CVE JSON 5 record, look for containers.adp[] with providerMetadata.shortName equal to CISA-ADP. Its metrics[] array holds other objects, two of which matter here. From the current record for GitLab CVE-2026-97229:

{"type": "ssvc", "content": {"id": "CVE-2026-97229", "role": "CISA Coordinator",
  "options": [{"Exploitation": "active"}, {"Automatable": "..."}, {"Technical Impact": "..."}],
  "version": "2.0.3", "timestamp": "..."}}
{"type": "kev", "content": {"dateAdded": "2026-10-29",
  "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-97229"}}

(Automatable, Technical Impact and the timestamp are elided; the Vulnrichment explainer covers all three SSVC values.)

The CISA Vulnrichment README states the rule for the second block: “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.” The SSVC values come from the CISA Coordinator decision tree; the SSVC project’s Exploitation decision point defines active as “Shared, observable, reliable evidence that the exploit is being used in the wild by real attackers; there is credible public reporting”, and none as no evidence of active exploitation and no public proof of concept.

FieldValuesWhat a change means
ssvc Exploitationnone, poc, activeCISA’s current assessment of exploitation state
kev dateAddeda dateThe CVE is on the KEV catalog; date matches the catalog
cveMetadata.statePUBLISHED, REJECTEDA rejected record keeps no ADP containers

How we measured

We cloned CVEProject/cvelistV5 without blobs and ran git diff --name-status between the two tags. The cve_2026-10-17_0000Z tag points at a commit made 2026-10-16 23:29 UTC; cve_2026-11-16_0000Z at 2026-11-16 00:15 UTC. That produced 31,312 changed CVE files: 16,690 added and 14,622 modified. We fetched both versions of each modified record and the new version of each added record from raw.githubusercontent.com at the two commits, then compared the CISA-ADP values. KEV comparisons used the kev-data JSON as of November 16, 2026.

A two-point diff only sees the start and end state, so a record that went none to poc to active inside the window counts once, as none to active.

What moved in 30 days

Change in CISA-ADP Exploitation (modified records)Records
no SSVC block → none2,389
no SSVC block → poc282
none → active14
none → poc10
poc → none5
no SSVC block → active2
none or poc → no SSVC block19

All 19 losses were records that changed from PUBLISHED to REJECTED; none of the 672 rejected records in the changed set carries an ADP container. (29 modified records were rejected in the window in total; the other 10 had no CISA-ADP SSVC to lose.) The CVE record states post covers what a rejection means for triage.

Of the 16,690 records first published in the window, 12,071 arrived with Exploitation none, 1,940 with poc, 18 with active and 2,661 with no CISA-ADP SSVC block yet.

Two findings matter for alerting:

  1. active tracked KEV exactly. All 34 records that gained active (16) or were published with it (18) were on the KEV catalog. In this window, alerting on active would not have told you about any CVE that the KEV feed did not.
  2. Exploitation can go down. Five records went from poc to none. Store the current value and alert on increases; do not assume the field only ratchets upward.

How closely the kev block followed the catalog

CISA added 33 CVEs to KEV with a dateAdded between October 17 and November 15, 2026. By the November 16 snapshot:

  • 31 had a CISA-ADP kev block whose dateAdded matched the catalog.
  • All 33 had SSVC Exploitation active.
  • Two had active but no kev block: Adobe CVE-2026-48356 and Google CVE-2026-111497, both added to KEV on October 27. Their CISA-ADP containers were last updated on October 28 with only the SSVC entry.

For the 31 with a block, the CISA-ADP container’s dateUpdated fell one calendar day after the KEV dateAdded for 28 CVEs, two days later for 2 (the PHP pair CVE-2026-109618 and CVE-2026-109619) and four days later for 1 (Ivanti CVE-2026-118527). Most updates landed between 03:55 and 04:57 UTC. Because dateUpdated is the container’s last update, it is an upper bound on when the block appeared, not an exact timestamp. The KEV catalog’s own dateAdded is a date with no time.

The practical reading: the record-level kev block is a copy that typically lags the catalog by about a day and occasionally does not arrive. If you need same-day KEV alerts, read the catalog. The KEV JSON feed field guide covers matching it against a scanner export.

A watcher that diffs CISA-ADP signals

The script below reads cvelistV5’s delta.json (the change list described in the delta.json and deltaLog.json guide), fetches each new or updated record, extracts the CISA-ADP signals and compares them with a local state file. It alerts on a new kev block, an increase in Exploitation to poc or active, and a change to REJECTED. Python 3 standard library only.

#!/usr/bin/env python3
"""Alert when a CVE record's CISA-ADP container gains a KEV block or a new SSVC Exploitation value.

Usage:
  python3 adp_watch.py state.json                 # read cvelistV5 delta.json, fetch changed records
  python3 adp_watch.py state.json rec1.json ...   # offline: compare local record files
"""
import json, sys, urllib.request

DELTA = "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/delta.json"
RANK = {None: 0, "none": 1, "poc": 2, "active": 3}

def signals(rec):
    s = {"state": rec["cveMetadata"]["state"], "exploitation": None, "kev": None}
    for adp in rec.get("containers", {}).get("adp", []) or []:
        if adp.get("providerMetadata", {}).get("shortName") != "CISA-ADP":
            continue
        for m in adp.get("metrics", []) or []:
            other = m.get("other") or {}
            if other.get("type") == "ssvc":
                for opt in other["content"].get("options", []):
                    if "Exploitation" in opt:
                        s["exploitation"] = opt["Exploitation"]
            elif other.get("type") == "kev":
                s["kev"] = other["content"].get("dateAdded")
    return s

def compare(cve, old, new):
    alerts = []
    if new["state"] == "REJECTED" and (old or {}).get("state") != "REJECTED":
        alerts.append(f"{cve}: record REJECTED, ADP data removed")
    if new["kev"] and not (old or {}).get("kev"):
        alerts.append(f"{cve}: KEV block added (dateAdded {new['kev']})")
    o = (old or {}).get("exploitation")
    if RANK.get(new["exploitation"], 0) > RANK.get(o, 0) and new["exploitation"] in ("poc", "active"):
        alerts.append(f"{cve}: SSVC Exploitation {o} -> {new['exploitation']}")
    return alerts

def get(url):
    with urllib.request.urlopen(url, timeout=30) as r:
        return json.load(r)

def main():
    state_path, files = sys.argv[1], sys.argv[2:]
    try:
        state = json.load(open(state_path))
    except FileNotFoundError:
        state = {}
    if files:
        records = [json.load(open(f)) for f in files]
    else:
        delta = get(DELTA)
        print(f"delta fetchTime {delta['fetchTime']}: {delta['numberOfChanges']} changes")
        records = [get(e["githubLink"]) for k in ("new", "updated") for e in delta.get(k, [])]
    for rec in records:
        cve = rec["cveMetadata"]["cveId"]
        new = signals(rec)
        for a in compare(cve, state.get(cve), new):
            print("ALERT", a)
        state[cve] = new
    json.dump(state, open(state_path, "w"), indent=1)

if __name__ == "__main__":
    main()

How we ran it (Python 3.13, November 16, 2026): feeding the October 17 version and then the November 16 version of CVE-2026-97229 printed:

ALERT CVE-2026-97229: KEV block added (dateAdded 2026-10-29)
ALERT CVE-2026-97229: SSVC Exploitation none -> active

The same two-step test on CVE-2023-54404 printed record REJECTED, ADP data removed. A live run against delta.json (fetchTime 2026-11-16T03:48:36Z, one change) fetched the record and wrote state without alerting.

Limits of the script as written: it fetches records one at a time, so a large delta is slow; delta.json only holds the latest batch, so a missed run loses changes unless you replay deltaLog.json as the delta guide describes; and a CVE seen for the first time with poc or active alerts immediately, which is what you want for new records but noisy on the first run. Filter to the CVEs in your inventory before alerting, and seed the state file from a full snapshot before going live. Treat it as a starting point, not production code.

Wiring it into a patch decision

  • KEV feed first. Poll the KEV JSON and alert on new cveID values in your inventory. In our window it was never behind the CVE record.
  • CISA-ADP diff second. Use it for poc changes, SSVC values on CVEs that will never reach KEV, and rejections that should close tickets.
  • Re-score on change. An Exploitation change moves the SSVC outcome; feed it back into the decision step of the prioritization workflow rather than paging on every poc.
  • Watch the ransomware flag separately. KEV’s knownRansomwareCampaignUse changes in the catalog only; see KEV ransomware flag flips.

Limits of this article

  • One 30-day window. The finding that active matched KEV exactly is an observation for October 17 to November 16, 2026, not a documented CISA rule.
  • Two-point diff: intermediate states inside the window are not visible.
  • Lag figures use the CISA-ADP container’s last dateUpdated, which can be later than the moment the kev block first appeared.
  • The two missing kev blocks were missing as of the November 16 snapshot; they may be added later.

Sources and verification

Important claimSourceStatus
CISA-ADP adds a KEV block only for KEV CVEscisagov/vulnrichment READMEVerified
SSVC Exploitation definitionsCERTCC/SSVC exploitation.pyVerified
31,312 changed records; transition counts; 34 active, all in KEVcvelistV5 tags cve_2026-10-17_0000Z and cve_2026-11-16_0000Z, our scriptVerified (computed)
33 KEV adds Oct 17 to Nov 15; 31 with kev block; lag 1/2/4 dayscisagov/kev-data, CVE records at cve_2026-11-16_0000ZVerified (computed); lag qualified as upper bound
CVE-2026-48356 and CVE-2026-111497 lack a kev blockCVE records at cve_2026-11-16_0000ZVerified as of that snapshot
Watcher outputRun on November 16, 2026Verified

Frequently asked questions

Where does a CVE record say a vulnerability is exploited?

In the CISA-ADP container: containers.adp[] where providerMetadata.shortName is CISA-ADP. Its metrics[].other entries hold an ssvc object whose content.options include an Exploitation value, and, for CVEs on the KEV catalog, a kev object with content.dateAdded and a reference URL. The CNA container has no standard exploitation field.

Is SSVC Exploitation active the same as being on CISA KEV?

Not by definition: SSVC defines active as shared, observable, reliable evidence of in-the-wild use with credible public reporting, while KEV has its own listing criteria. In our 30-day diff, every record that gained or was published with active was a KEV CVE, but that is one month of data, not a rule.

How quickly does the KEV block appear in the CVE record?

For 31 KEV additions between October 17 and November 15, 2026 that had a kev block by November 16, the CISA-ADP container's dateUpdated was one day after the KEV dateAdded for 28, two days for 2 and four days for 1. dateUpdated is the container's last update, so it bounds when the block appeared rather than recording it exactly.

Should I alert on the KEV feed or on CVE records?

Alert on the KEV JSON feed first, because it is the source the ADP kev block copies and it was never behind in our data. Diff CISA-ADP as well if you want poc changes, SSVC values for CVEs that are not on KEV, and REJECTED state changes in the same pipeline.

Vulnerability ManagementCisa-AdpVulnrichmentSsvcKevCvelistv5AlertingCve Json 5