Skip to content

Added to CISA KEV

What a record said when it was published, what it says now, and the commit that changed it.

14 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Added to CISA KEV" from Google, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
Fri 4 Sep 2026· 1 record change
2026-09-04CVE-2026-85046
GoogleChromium V8
CISA KEV
fix due 2026-09-18Not applicable: Added to CISA KEV has no earlier value
Tue 9 Jun 2026· 1 record change
2026-06-09CVE-2026-11645
GoogleChromium V8
CISA KEV
fix due 2026-06-23Not applicable: Added to CISA KEV has no earlier value
Wed 1 Apr 2026· 1 record change
2026-04-01CVE-2026-5281
GoogleDawn
CISA KEV
fix due 2026-04-15Not applicable: Added to CISA KEV has no earlier value
Fri 13 Mar 2026· 2 record changes
2026-03-13CVE-2026-3910
GoogleChromium V8
CISA KEV
fix due 2026-03-27Not applicable: Added to CISA KEV has no earlier value
2026-03-13CVE-2026-3909
GoogleSkia
CISA KEV
fix due 2026-03-27Not applicable: Added to CISA KEV has no earlier value
Tue 17 Feb 2026· 1 record change
2026-02-17CVE-2026-2441
GoogleChromium
CISA KEV
fix due 2026-03-10Not applicable: Added to CISA KEV has no earlier value
Fri 12 Dec 2025· 1 record change
2025-12-12CVE-2025-14174
GoogleChromium
CISA KEV
fix due 2026-01-02Not applicable: Added to CISA KEV has no earlier value
Wed 19 Nov 2025· 1 record change
2025-11-19CVE-2025-13223
GoogleChromium V8
CISA KEV
fix due 2025-12-10Not applicable: Added to CISA KEV has no earlier value
Tue 23 Sep 2025· 1 record change
2025-09-23CVE-2025-10585
GoogleChromium V8
CISA KEV
fix due 2025-10-14Not applicable: Added to CISA KEV has no earlier value
Tue 22 Jul 2025· 1 record change
2025-07-22CVE-2025-6558
GoogleChromium
CISA KEV
fix due 2025-08-12Not applicable: Added to CISA KEV has no earlier value
Wed 2 Jul 2025· 1 record change
2025-07-02CVE-2025-6554
GoogleChromium V8
CISA KEV
fix due 2025-07-23Not applicable: Added to CISA KEV has no earlier value
Mon 9 Jun 2025· 1 record change
2025-06-09CVE-2025-5419
GoogleChromium V8
CISA KEV
fix due 2025-06-26 · listed 2025-06-05Not applicable: Added to CISA KEV has no earlier value
Thu 15 May 2025· 1 record change
2025-05-15CVE-2025-4664
GoogleChromium
CISA KEV
fix due 2025-06-05Not applicable: Added to CISA KEV has no earlier value
Thu 27 Mar 2025· 1 record change
2025-03-27CVE-2025-2783
GoogleChromium Mojo
CISA KEV
fix due 2025-04-17Not applicable: Added to CISA KEV has no earlier value

This kind is counted once per CVE record, so changes and records are the same number here. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 12:43 UTC · scroll for earlierfewermore

Data sources and quality

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Check my CVEs against these changes →