# KEV lag

GLOSSARY, read 10 Nov 2026

**Definition.** KEV lag is this site's measure: the days from the NVD published date to the CISA KEV dateAdded, in UTC calendar days. Across 318 additions from 2025-11-10 to 2026-11-09 the median is 10.5 days, 45.3 percent were listed within 7 days and 17.3 percent more than a year after publication.

A negative or zero lag means the entry was listed before or on the day NVD published it: 8 additions were negative and 61 were zero, 69 in all (21.7 percent). Only 11 of those 69 had an EPSS score on listing day, which is part of why only 260 of 318 rows carry one.

The lag is a property of the catalog, not of any one program. It is the reason a ranking cannot wait for a KEV listing alone: the middle entry waited 10.5 days, and the 75th percentile waited 146 days.

## A sourced example

CVE-2026-33824 was published by NVD on 2026-04-14 and added to KEV on 2026-08-18, a KEV lag of 126 days, while CVE-2026-60004 (Gitea) was added on 2026-08-25, one day before NVD published it on 2026-08-26, a lag of -1.

## Related terms

- [KEV dateAdded](/glossary/kev-date-added/)
- [EPSS probability](/glossary/epss-probability/)

## Sources

- Source for the example: KEV lag: https://nvd.nist.gov/vuln/detail/CVE-2026-33824 (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://epssvscvss.com/glossary/kev-lag/
