Were we right, and were we early?
Any tracker can mirror CISA's KEV catalog after the fact. This page checks whether our own reporting existed before CISA's official confirmation — computed directly from our publish dates against CISA's listing dates, not asserted. The query that generates this page is public; see the methodology note below.
Fastest calls on record
| CVE | Editor | We published | CISA listed KEV | Lead time |
|---|---|---|---|---|
| CVE-2026-111357 | + Patch & Defense | October 30, 2026 | October 30, 2026 | same day |
| CVE-2026-118527 | + Patch & Defense | October 30, 2026 | October 30, 2026 | same day |
| CVE-2026-76418 | + Patch & Defense | October 29, 2026 | October 29, 2026 | same day |
| CVE-2026-41709 | + Patch & Defense | October 28, 2026 | October 28, 2026 | same day |
| CVE-2026-46300 | + Patch & Defense | October 28, 2026 | October 28, 2026 | same day |
| CVE-2026-111497 | + Patch & Defense | October 27, 2026 | October 27, 2026 | same day |
| CVE-2026-48356 | + Patch & Defense | October 27, 2026 | October 27, 2026 | same day |
| CVE-2026-110936 | ? Vulnerability Watch | October 20, 2026 | October 20, 2026 | same day |
| CVE-2026-96656 | ~ Analysis | October 20, 2026 | October 20, 2026 | same day |
| CVE-2026-102764 | + Patch & Defense | October 16, 2026 | October 16, 2026 | same day |
| CVE-2026-0322 | ~ Analysis | October 14, 2026 | October 14, 2026 | same day |
| CVE-2026-104935 | + Patch & Defense | October 13, 2026 | October 13, 2026 | same day |
| CVE-2026-88779 | + Patch & Defense | October 4, 2026 | October 4, 2026 | same day |
| CVE-2026-104286 | + Patch & Defense | October 1, 2026 | October 1, 2026 | same day |
| CVE-2026-76504 | + Patch & Defense | September 30, 2026 | September 30, 2026 | same day |
What's counted: only CVE entries a named editor actually wrote, that are currently confirmed KEV or exploited-in-wild, and where we have both our own publish date and CISA's official KEV-listing date (kevDateAdded) to compare.
What's excluded: the roughly 1,600 CVE entries oursync process auto-backfilled directly from CISA's own catalog, to fill out the KEV tracker. Those entries' publish dates are mechanically set to CISA's own listing date — including them would inflate this number for free, so they're not counted.
What "lead time" does and doesn't mean: a large lead-time number sometimes means we happened to cover a CVE for general disclosure reasons long before CISA later confirmed active exploitation on it — not that we predicted the exploitation. Either way, the claim is narrow and literal: our reporting existed, and was accurate, before CISA's official confirmation. Dates are shown in full above so you can judge each one yourself.