# KEV dueDate

GLOSSARY, read 10 Nov 2026

**Definition.** The dueDate field in the KEV catalog is the date by which federal civilian agencies must remediate the entry. In the KEV feed, dueDate minus dateAdded is 3 days for 124 of the 156 ledger entries added on or after 2026-06-10, when BOD 26-04 took effect, and 14 days for the other 32.

Before 2026-06-10, under the earlier directive, the same feed shows a different spread for the 162 ledger entries: 66 at 21 days, 55 at 14 days, 31 at 3 days, 7 at 7 days, 2 at 2 days and 1 at 5 days. Compare a due date only with its own dateAdded.

BOD 26-04 starts the clock at the earlier of KEV listing or the agency identifying the vulnerability on an asset, and says timelines are dynamic as facts change. A private program can borrow the structure, but the dueDate itself is a federal obligation.

## A sourced example

CISA's catalog lists CVE-2026-33824 with dateAdded 2026-08-18 and dueDate 2026-08-21, a 3-day window.

## Related terms

- [KEV dateAdded](/glossary/kev-date-added/)
- [BOD 22-01](/glossary/bod-22-01/)
- [Known ransomware campaign use](/glossary/known-ransomware-campaign-use/)

## Sources

- Source for the example: KEV dueDate: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (read 10 Nov 2026)

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