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.

13 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Added to CISA KEV" from Fortinet, 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.
Mon 27 Jul 2026· 1 record change
2026-07-27CVE-2025-68686
FortinetFortiOS
CISA KEV
fix due 2026-08-10Not applicable: Added to CISA KEV has no earlier value
Thu 16 Jul 2026· 2 record changes
2026-07-16CVE-2026-25089
FortinetFortiSandbox
CISA KEV
fix due 2026-07-19Not applicable: Added to CISA KEV has no earlier value
2026-07-16CVE-2026-39808
FortinetFortiSandbox
CISA KEV
fix due 2026-07-19Not applicable: Added to CISA KEV has no earlier value
Mon 13 Apr 2026· 1 record change
2026-04-13CVE-2026-21643
FortinetFortiClient EMS
CISA KEV
fix due 2026-04-16Not applicable: Added to CISA KEV has no earlier value
Mon 6 Apr 2026· 1 record change
2026-04-06CVE-2026-35616
FortinetFortiClient EMS
CISA KEV
fix due 2026-04-09Not applicable: Added to CISA KEV has no earlier value
Tue 27 Jan 2026· 1 record change
2026-01-27CVE-2026-24858
FortinetMultiple Products
CISA KEV
fix due 2026-01-30Not applicable: Added to CISA KEV has no earlier value
Tue 16 Dec 2025· 1 record change
2025-12-16CVE-2025-59718
FortinetMultiple Products
CISA KEV
fix due 2025-12-23Not applicable: Added to CISA KEV has no earlier value
Tue 18 Nov 2025· 1 record change
2025-11-18CVE-2025-58034
FortinetFortiWeb
CISA KEV
fix due 2025-11-25Not applicable: Added to CISA KEV has no earlier value
Fri 14 Nov 2025· 1 record change
2025-11-14CVE-2025-64446
FortinetFortiWeb
CISA KEV
fix due 2025-11-21Not applicable: Added to CISA KEV has no earlier value
Fri 18 Jul 2025· 1 record change
2025-07-18CVE-2025-25257
FortinetFortiWeb
CISA KEV
fix due 2025-08-08Not applicable: Added to CISA KEV has no earlier value
Wed 25 Jun 2025· 1 record change
2025-06-25CVE-2019-6693
FortinetFortiOS
CISA KEV
fix due 2025-07-16Not applicable: Added to CISA KEV has no earlier value
Wed 14 May 2025· 1 record change
2025-05-14CVE-2025-32756
FortinetMultiple Products
CISA KEV
fix due 2025-06-04Not applicable: Added to CISA KEV has no earlier value
Tue 18 Mar 2025· 1 record change
2025-03-18CVE-2025-24472
FortinetFortiOS and FortiProxy
CISA KEV
fix due 2025-04-08Not 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 03:47 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 →