KEV Time to Listing: CVE datePublished to dateAdded

How long after a CVE record is published does CISA add it to KEV? We joined all 1,769 KEV entries to their CVE records' datePublished. For 2026 additions the median gap is 14 days, but the catalog mixes same-week listings with backfills of decade-old CVEs. Numbers by year and vendor, a tested script, and what it means for SLA clocks.

A pale blue-grey multiple-exposure image of several pocket-watch and stopwatch dials overlapping, their hands pointing in different directions
Photo by Daniele Levis Pelusi on Unsplash

For CVEs that CISA added to its Known Exploited Vulnerabilities (KEV) catalog in 2026, the median gap between the CVE record’s publication and the KEV dateAdded is 14 days. For 2026 CVE IDs it is 4 days, and 28% of those were listed on or before the day their record went public. But the same catalog also backfills old bugs: 18% of this year’s additions were published more than a year before they were listed.

That split is the useful part for anyone who sets patch SLAs. A KEV due date starts its clock at listing; your exposure clock started at publication. This article measures the gap between the two across the whole catalog, by year and by vendor, and gives you a script to rerun the numbers yourself. For where KEV sits in the full triage flow, see our vulnerability prioritization workflow from CVE record to ticket.

What we measured

  • KEV side: dateAdded for every entry in the KEV JSON (catalog version 2026.11.06, released 2026-11-06T19:44Z, 1,769 entries). Our field guide to the KEV JSON feed covers the other fields.
  • CVE side: cveMetadata.datePublished from each entry’s record in the cvelistV5 bulk release tagged cve_2026-11-09_0000Z. All 1,769 KEV CVEs had a record, all in the PUBLISHED state.
  • Gap: dateAdded − date(datePublished) in whole days. Negative means KEV listed the CVE before the record was published.

The CVE Record Format schema defines datePublished as “The date/time the CVE Record was first published in the CVE List.” That is not the vendor’s advisory date or the first public report, which can be earlier, so treat the gap as “time since the CVE record existed”, not “time since disclosure”. KEV’s dateAdded is a date with no time zone, so a gap of 0 or ±1 day is within rounding.

CISA lists three criteria for adding an entry: the vulnerability “has an assigned Common Vulnerabilities and Exposures (CVE) ID”, there is “reliable evidence that the vulnerability has been actively exploited in the wild”, and there is “a clear remediation action for the vulnerability, such as a vendor-provided update.” The gap therefore reflects when exploitation evidence reached CISA, not processing speed.

The gap by year

The catalog launched on 2021-11-03 with 287 entries at once, which is why 2021 and 2022 look so different from later years: the early catalog was mostly a backlog of known-exploited older CVEs.

Year addedEntriesMedian gap (days)Listed on/before publication dayWithin 7 daysWithin 30 daysMore than 365 days
20213114462%3%6%56%
20225551,4367%9%12%75%
20231871224%45%55%25%
202418621.521%42%51%24%
20252452620%40%51%23%
2026 (to Nov 6)2851419%43%59%18%

Since 2023 the shape has been stable: roughly a fifth of entries are listed by the day the record is published, a little over two fifths within a week, and about a quarter or less are CVEs more than a year old.

Fresh CVEs versus backfill

Splitting 2026 additions by CVE ID year separates the two populations. The 197 entries with 2026 IDs had a median gap of 4 days: 28% were listed on or before publication day, 60% within 7 days and 82% within 30 days. The rest are mostly backfill. Of all 285 entries added in 2026, 51 were published more than 365 days before listing; the oldest is CVE-2008-4128 (Cisco), listed about 6,500 days after its record was published.

The same pattern holds in earlier years. For same-year CVE IDs, the median gap was 2 days in 2023, 3 in 2024 and 3 in 2025.

The gap by vendor

For entries added in 2025 and 2026, vendors with at least eight additions:

Vendor (vendorProject)EntriesMedian gap (days)On/before publication dayWithin 7 daysMore than 365 days
Microsoft79149%54%24%
Cisco28346%57%11%
Apple19216%53%21%
Fortinet17729%53%6%
Google16125%100%0%
Linux161320%0%38%
Ivanti15633%60%0%
Citrix11736%55%0%
Adobe10580%30%30%
SonicWall10140%70%20%
Oracle9480%22%33%
Synacor92800%0%33%

Two readings, both cautious because the samples are small:

  • Vendors that publish exploited-in-the-wild status with the fix (Microsoft, Cisco, Google, SonicWall) show median gaps of one to three days. For Microsoft, almost half the entries were listed on or before the day the CVE record appeared. If your SLA for these products waits for KEV, it waits very little, but it still waits.
  • Linux kernel entries behave differently: a median of 132 days and none within a week. Kernel CVE records are published in volume by the kernel CNA, and exploitation evidence for a specific one usually arrives much later. Our guide to Linux kernel CVE records and stable-branch ranges covers how to tell whether you are affected once it does.

Microsoft’s 24% over a year reflects backfill of old Windows and Office CVEs (several from 2008-2009 were added in 2026), not slow listing of new ones.

KEV can come before the CVE record

62 entries have a negative gap: KEV listed them before their CVE record was published. Four were added in 2026, including CVE-2026-118527 (Ivanti Connect Secure), added on 2026-10-30 with a record published on 2026-11-03, and CVE-2026-87886, added on 2026-09-16 one day before its record.

Some older negative gaps are artefacts: 210 KEV CVE records carry a datePublished with a midnight timestamp, typical of records migrated from the legacy CVE format, and a few of those dates are clearly later than the CVE’s real disclosure. Treat large negative gaps on pre-2023 CVEs as data quality, not as evidence of early listing.

The engineering consequence is the same either way: join KEV to your inventory by cveID alone. A pipeline that only checks KEV membership for CVEs it has already ingested from the CVE List or NVD will skip the entries CISA lists first, which are exactly the most urgent ones.

What this means for SLA clocks

Two clocks, both worth storing. The KEV dueDate is set from dateAdded. For 2026 additions it was 3 days after listing for 151 entries, 14 days for 87 and 21 days for 44; our BOD 26-04 explainer covers where those tiers come from. Measured from datePublished instead, the median 2026 entry was due 22 days after its record appeared. If you only report “days since KEV listing”, your metrics will look better than your actual exposure window.

Do not use KEV as the start signal for internet-facing products. For fresh CVEs in edge and enterprise products the median wait for a listing is a few days, and attackers were by definition already active when CISA got its evidence. KEV confirms urgency; it should not be the first thing that creates it. EPSS has the same lag problem for new KEV entries, as our EPSS-for-KEV audit showed.

Treat backfill as a reopen trigger. Nearly one in five 2026 additions was a CVE more than a year old. If your team accepted risk on an old CVE (“internal only”, “no known exploit”), a KEV listing invalidates the second half of that reasoning. Alert on any new KEV cveID that matches an open risk acceptance or a suppressed finding, not only on new scanner findings.

Watch for the CISA-ADP update too. In our snapshot, 1,767 of the 1,769 KEV CVE records also carried a kev metric in a CISA-ADP container, so the listing shows up in the CVE record itself; our Vulnrichment SSVC guide explains the Exploitation value, and the cvelistV5 delta sync guide shows how to pick up those updates hourly.

A script to rerun the numbers

This Python 3 script (standard library only) pulls the KEV JSON, fetches each recent entry’s CVE record from cvelistV5 on GitHub, and prints the gap. We ran it on 2026-11-09 with the default 90-day window:

#!/usr/bin/env python3
"""Days from CVE record publication to CISA KEV listing, for recent KEV adds.
Usage: python3 kev_lag.py [days_back]   (default 90)"""
import json, sys, urllib.request
from datetime import date, timedelta
from statistics import median

KEV = "https://raw.githubusercontent.com/cisagov/kev-data/main/known_exploited_vulnerabilities.json"
CVE = "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/{y}/{b}xxx/{id}.json"

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

def record_url(cve_id):
    _, year, num = cve_id.split("-")
    return CVE.format(y=year, b=num[:-3] if len(num) > 3 else "0", id=cve_id)

days_back = int(sys.argv[1]) if len(sys.argv) > 1 else 90
cutoff = date.today() - timedelta(days=days_back)
kev = get(KEV)
rows = []
for v in kev["vulnerabilities"]:
    added = date.fromisoformat(v["dateAdded"])
    if added < cutoff:
        continue
    try:
        meta = get(record_url(v["cveID"]))["cveMetadata"]
        published = date.fromisoformat(meta["datePublished"][:10])
        lag = (added - published).days
    except Exception:           # no CVE record in cvelistV5 yet (404)
        published, lag = None, None
    rows.append((v["cveID"], v["vendorProject"], str(published), v["dateAdded"], lag))

for r in sorted(rows, key=lambda r: r[3]):
    print("\t".join(map(str, r)))
lags = [r[4] for r in rows if r[4] is not None]
print(f"\nKEV adds since {cutoff}: {len(rows)}; with a CVE record: {len(lags)}")
if lags:
    print(f"median lag {median(lags)} days; listed on or before publication day: "
          f"{sum(l <= 0 for l in lags)}; within 7 days: {sum(l <= 7 for l in lags)}; "
          f"older than 365 days: {sum(l > 365 for l in lags)}")

The last lines of our run:

CVE-2026-118527	Ivanti	2026-11-03	2026-10-30	-4
CVE-2026-111357	Ivanti	2026-10-15	2026-10-30	15
CVE-2026-119977	WordPress	2026-10-31	2026-11-03	3
CVE-2024-27834	Apple	2024-05-13	2026-11-04	905
CVE-2026-19868	SonicWall	2026-11-06	2026-11-06	0

KEV adds since 2026-08-11: 107; with a CVE record: 107
median lag 8 days; listed on or before publication day: 24; within 7 days: 53; older than 365 days: 13

The figures matched our corpus-wide calculation for the same window. The script makes one HTTP request per KEV entry in the window; for the whole catalog, download a cvelistV5 bulk release zip instead, as we did for the tables above. To turn the output into an alert, swap the print loop for a check of each new cveID against your asset inventory and open risk acceptances.

Limits of this article

  • datePublished is the CVE record’s publication date, not the earliest public disclosure. For CVEs where a vendor advisory or exploit write-up came first, the real exposure window is longer than our gap.
  • Pre-2023 records include migrated legacy dates; we did not correct them. The 2021-2022 rows describe the catalog’s backlog phase and should not be compared directly with later years.
  • Vendor rows with 8 to 20 entries are small samples. They show a pattern, not a vendor benchmark.
  • We measured when CISA listed entries, not when exploitation started. KEV does not publish a first-seen-exploited date.

Sources and verification

Important claimSourceStatus
KEV catalog 2026.11.06, 1,769 entries, dateAdded and dueDate valuescisagov/kev-dataVerified (data)
datePublished for all 1,769 KEV CVEs, all PUBLISHEDCVEProject/cvelistV5, release cve_2026-11-09_0000ZVerified (data)
Definition of datePublishedCVE Record Format schemaVerified
1,767 of 1,769 KEV CVE records carry a CISA-ADP kev metriccvelistV5 release cve_2026-11-09_0000ZVerified (data)
KEV inclusion criteriaCISA KEV pageVerified
All medians, shares and counts in the tablesFirewallSync calculation from the two datasets aboveVerified (recomputed with code)
Reasons for vendor differences (advisory practice, kernel CNA volume)Editorial interpretationQualified

Frequently asked questions

How long does CISA take to add a vulnerability to KEV?

Measured from the CVE record's datePublished to KEV's dateAdded, the median for entries added in 2026 is 14 days (catalog 2026.11.06). For 2026 CVE IDs added in 2026 it is 4 days, and 28% were listed on or before the day the record was published. CISA adds entries when it has reliable evidence of exploitation, so the gap measures when evidence arrived, not how slow CISA is.

Can a CVE be in KEV before the CVE record is published?

Yes. 62 KEV entries have a dateAdded earlier than their record's datePublished, including CVE-2026-118527 (Ivanti Connect Secure), added on October 30, 2026 with a record published on November 3. A pipeline that only checks KEV for CVEs it has already ingested from the CVE List or NVD will miss these.

Does CISA add old CVEs to KEV?

Yes, regularly. Of the 285 entries added in 2026, 51 were for CVEs published more than 365 days earlier, the oldest being CVE-2008-4128 (Cisco), about 17.8 years after publication. New exploitation evidence for an old bug is a reason to recheck systems where that CVE was accepted as low risk.

Should my patch SLA start at CVE publication or at KEV listing?

Both, for different questions. The KEV dueDate is set from dateAdded, so compliance tracking starts there. Exposure starts at publication, and for 2026 CVEs the median wait for a KEV listing was 4 days, so waiting for KEV before patching internet-facing systems gives up that head start.

Cisa KevCve RecordVulnerability PrioritizationPatch SlaVulnerability ManagementSecurity Operations