Product added

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

23 changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

PublisherPublishedChangedSourceRows

Counted changes of "Product added" published by 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 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 12 Aug 2026· 3 record changes
2026-08-12	CVE-2025-61848	fortinet	not named as affected at publication, now names fortianalyzer-bigdata	Days to revision 120
2026-08-12	CVE-2023-42787	fortinet	not named as affected at publication, now names fortianalyzer cloud	Days to revision 1,037
2026-08-12	CVE-2023-42787	fortinet	not named as affected at publication, now names fortianalyzer-bigdata	Days to revision 1,037
Wed 8 Jul 2026· 5 record changes
2026-07-08	CVE-2024-33503	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 540
2026-07-08	CVE-2024-35276	fortinet	not named as affected at publication, now names fortianalyzer cloud	Days to revision 540
2026-07-08	CVE-2024-35276	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 540
2026-07-08	CVE-2024-45331	fortinet	not named as affected at publication, now names fortianalyzer cloud	Days to revision 538
2026-07-08	CVE-2023-42789	fortinet	not named as affected at publication, now names fortisase	Days to revision 848
Tue 23 Jun 2026· 2 record changes
2026-06-23	CVE-2025-25250	fortinet	not named as affected at publication, now names fortisase	Days to revision 378
2026-06-23	CVE-2025-54821	fortinet	not named as affected at publication, now names fortisase	Days to revision 217
Tue 9 Jun 2026· 1 record change
2026-06-09	CVE-2026-24858	fortinet	not named as affected at publication, now names fortinac-f	Days to revision 133
Tue 12 May 2026· 1 record change
2026-05-12	CVE-2026-25836	fortinet	not named as affected at publication, now names fortisandbox paas	Days to revision 63
Wed 28 Jan 2026· 2 record changes
2026-01-28	CVE-2026-24858	fortinet	not named as affected at publication, now names fortiproxy	Days to revision 1
2026-01-28	CVE-2026-24858	fortinet	not named as affected at publication, now names fortiweb	Days to revision 1
Tue 27 Jan 2026· 2 record changes
2026-01-27	CVE-2024-50571	fortinet	not named as affected at publication, now names fortianalyzer cloud	Days to revision 105
2026-01-27	CVE-2024-50571	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 105
Wed 14 Jan 2026· 7 record changes
2026-01-14	CVE-2024-54026	fortinet	not named as affected at publication, now names fortisandbox cloud	Days to revision 309
2026-01-14	CVE-2023-41842	fortinet	not named as affected at publication, now names fortianalyzer-bigdata	Days to revision 673
2026-01-14	CVE-2024-48884	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 365
2026-01-14	CVE-2024-50566	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 365
2026-01-14	CVE-2025-31366	fortinet	not named as affected at publication, now names fortisase	Days to revision 92
2026-01-14	CVE-2025-47890	fortinet	not named as affected at publication, now names fortisase	Days to revision 92
2026-01-14	CVE-2024-47569	fortinet	not named as affected at publication, now names fortimanager cloud	Days to revision 92

This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. 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.

3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

Every kind of change

All kinds

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 →