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-20349 | + Patch & Defense | August 11, 2026 | August 11, 2026 | same day |
| CVE-2026-68820 | + Patch & Defense | August 11, 2026 | August 11, 2026 | same day |
| CVE-2026-20316 | + Patch & Defense | July 29, 2026 | July 29, 2026 | same day |
| CVE-2026-16812 | + Patch & Defense | July 27, 2026 | July 27, 2026 | same day |
| CVE-2026-16232 | + Patch & Defense | July 22, 2026 | July 22, 2026 | same day |
| CVE-2026-25089 | + Patch & Defense | July 16, 2026 | July 16, 2026 | same day |
| CVE-2026-46817 | + Patch & Defense | July 15, 2026 | July 15, 2026 | same day |
| CVE-2026-15409 | + Patch & Defense | July 14, 2026 | July 14, 2026 | same day |
| CVE-2026-15410 | + Patch & Defense | July 14, 2026 | July 14, 2026 | same day |
| CVE-2026-56155 | + Patch & Defense | July 14, 2026 | July 14, 2026 | same day |
| CVE-2026-56164 | + Patch & Defense | July 14, 2026 | July 14, 2026 | same day |
| CVE-2026-48908 | + Patch & Defense | July 7, 2026 | July 7, 2026 | same day |
| CVE-2026-55255 | + Patch & Defense | July 7, 2026 | July 7, 2026 | same day |
| CVE-2026-56290 | + Patch & Defense | July 7, 2026 | July 7, 2026 | same day |
| CVE-2026-48558 | + Patch & Defense | June 29, 2026 | June 29, 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.