Every change, newest first

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

133 changes · newest first · grouped by dayCSV JSON RSS

PublisherPublishedChangedSourceRows

Counted changes 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.	Kind	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 changed	Days 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.
Wed 14 Jan 2026· 7 record changes
2026-01-14	Product added	CVE-2024-54026	fortinet	not named as affected at publication, now names fortisandbox cloud	Days to revision 309
2026-01-14	Product added	CVE-2023-41842	fortinet	not named as affected at publication, now names fortianalyzer-bigdata	Days to revision 673
2026-01-14	Product added	CVE-2024-48884	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 365
2026-01-14	Product added	CVE-2024-50566	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 365
2026-01-14	Product added	CVE-2025-31366	fortinet	not named as affected at publication, now names fortisase	Days to revision 92
2026-01-14	Product added	CVE-2025-47890	fortinet	not named as affected at publication, now names fortisase	Days to revision 92
2026-01-14	Product added	CVE-2024-47569	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 92
Fri 19 Dec 2025· 1 record change
2025-12-19	Affected range extended	CVE-2023-44247	fortinetfortios	stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0.	Days to revision 584
Tue 16 Dec 2025· 1 record change
2025-12-16	Added to CISA KEV	CVE-2025-59718	FortinetMultiple Products CISA KEV	fix due 2025-12-23	Not applicable: Added to CISA KEV has no earlier value
Thu 11 Dec 2025· 1 record change
2025-12-11	Affected range extended	CVE-2025-59923	fortinetfortiauthenticator	stated at publication 6.6.4, now states 6.6.6Release branch starts at 6.6.0.	Days to revision 2
Wed 10 Dec 2025· 1 record change
2025-12-10	Affected range extended	CVE-2025-64471	fortinetfortiweb	stated at publication 7.6.4, now states 7.6.5Release branch starts at 7.6.0.	Days to revision 1
Tue 18 Nov 2025· 4 record changes
2025-11-18	Added to CISA KEV	CVE-2025-58034	FortinetFortiWeb CISA KEV	fix due 2025-11-25	Not applicable: Added to CISA KEV has no earlier value
2025-11-18	Affected range extended	CVE-2024-32122	fortinetfortios	stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.0.	Days to revision 224
2025-11-18	Affected range extended	CVE-2024-32122	fortinetfortios	stated at publication 7.4.7, now states 7.4.8Release branch starts at 7.4.0.	Days to revision 224
2025-11-18	Affected range extended	CVE-2024-32122	fortinetfortios	stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0.	Days to revision 224
Fri 14 Nov 2025· 1 record change
2025-11-14	Added to CISA KEV	CVE-2025-64446	FortinetFortiWeb CISA KEV	fix due 2025-11-21	Not applicable: Added to CISA KEV has no earlier value
Mon 3 Nov 2025· 1 record change
2025-11-03	Affected range extended	CVE-2025-24477	fortinetfortios	stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.4.	Days to revision 111
Thu 16 Oct 2025· 1 record change
2025-10-16	Affected range extended	CVE-2025-25255	fortinetfortiproxy	stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.1.	Days to revision 2
Fri 18 Jul 2025· 1 record change
2025-07-18	Added to CISA KEV	CVE-2025-25257	FortinetFortiWeb CISA KEV	fix due 2025-08-08	Not applicable: Added to CISA KEV has no earlier value
Mon 14 Jul 2025· 1 record change
2025-07-14	Ransomware use confirmed	CVE-2019-6693	FortinetFortiOS CISA KEV	stated at publication Unknown, now states Known	Days to revision 19
Wed 25 Jun 2025· 1 record change
2025-06-25	Added to CISA KEV	CVE-2019-6693	FortinetFortiOS CISA KEV	fix due 2025-07-16	Not applicable: Added to CISA KEV has no earlier value
Mon 9 Jun 2025· 1 record change
2025-06-09	Ransomware use confirmed	CVE-2024-21762	FortinetFortiOS CISA KEV	stated at publication Unknown, now states Known	Days to revision at least 103
Wed 14 May 2025· 1 record change
2025-05-14	Added to CISA KEV	CVE-2025-32756	FortinetMultiple Products CISA KEV	fix due 2025-06-04	Not applicable: Added to CISA KEV has no earlier value
Mon 7 Apr 2025· 1 record change
2025-04-07	Ransomware use confirmed	CVE-2022-42475	FortinetFortiOS CISA KEV	stated at publication Unknown, now states Known	Days to revision at least 41
Tue 18 Mar 2025· 2 record changes
2025-03-18	Added to CISA KEV	CVE-2025-24472	FortinetFortiOS and FortiProxy CISA KEV	fix due 2025-04-08	Not applicable: Added to CISA KEV has no earlier value
2025-03-18	Ransomware use confirmed	CVE-2024-55591	FortinetFortiOS and FortiProxy CISA KEV	stated at publication Unknown, now states Known	Days to revision at least 21
Fri 18 Oct 2024· 6 record changes
2024-10-18	Affected range extended	CVE-2023-28002	fortinetfortiproxy	stated at publication 2.0.13, now states 2.0.14Release branch starts at 2.0.0.	Days to revision 339
2024-10-18	Affected range extended	CVE-2023-28002	fortinetfortiproxy	stated at publication 7.2.7, now states 7.2.8Release branch starts at 7.2.0.	Days to revision 339
2024-10-18	Affected range extended	CVE-2023-28002	fortinetfortiproxy	stated at publication 7.0.13, now states 7.0.19Release branch starts at 7.0.0.	Days to revision 339
2024-10-18	Affected range extended	CVE-2023-28002	fortinetfortios	stated at publication 6.2.15, now states 6.2.16Release branch starts at 6.2.0.	Days to revision 339
2024-10-18	Affected range extended	CVE-2023-28002	fortinetfortios	stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0.	Days to revision 339
2024-10-18	Affected range extended	CVE-2023-28002	fortinetfortios	stated at publication 6.0.17, now states 6.0.18Release branch starts at 6.0.0.	Days to revision 339
Tue 21 May 2024· 1 record change
2024-05-21	Affected range extended	CVE-2023-47537	fortinetfortios	stated at publication 7.0.14, now states 7.0.15Release branch starts at 7.0.0.	Days to revision 96

Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. 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.

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →