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

Counted changes of "Product added" 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 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 changes
2026-08-122 commits	Show all 2 CVE records in this change: Product added: fortianalyzer-bigdata named as affected from fortinetHide the 2 CVE records in this change: Product added: fortianalyzer-bigdata named as affected from fortinet	fortinet	not named as affected at publication, now names fortianalyzer-bigdataBranches and original-value intervals are stated on each row.	Time to revision 120 to 1,037 days
2026-08-12	CVE-2025-61848	same vendor as the line above	same change as the line above	Time to revision 120 days
2026-08-12	CVE-2023-42787	same vendor as the line above	same change as the line above	Time to revision 1,037 days
2026-08-12	CVE-2023-42787	fortinet	not named as affected at publication, now names fortianalyzer cloud	Time to revision 1,037 days
Wed 8 Jul 2026· 5 changes
2026-07-08	Show all 2 CVE records in this change: Product added: fortimanager cloud named as affected from fortinetHide the 2 CVE records in this change: Product added: fortimanager cloud named as affected from fortinet	fortinet	not named as affected at publication, now names fortimanager cloud	Time to revision 540 days
2026-07-08	CVE-2024-33503	same vendor as the line above	same change as the line above	Time to revision 540 days
2026-07-08	CVE-2024-35276	same vendor as the line above	same change as the line above	Time to revision 540 days
2026-07-08	Show all 2 CVE records in this change: Product added: fortianalyzer cloud named as affected from fortinetHide the 2 CVE records in this change: Product added: fortianalyzer cloud named as affected from fortinet	fortinet	not named as affected at publication, now names fortianalyzer cloud	Time to revision 538 to 540 days
2026-07-08	CVE-2024-35276	same vendor as the line above	same change as the line above	Time to revision 540 days
2026-07-08	CVE-2024-45331	same vendor as the line above	same change as the line above	Time to revision 538 days
2026-07-08	CVE-2023-42789	fortinet	not named as affected at publication, now names fortisase	Time to revision 848 days
Tue 23 Jun 2026· 2 changes
2026-06-23	Show all 2 CVE records in this change: Product added: fortisase named as affected from fortinetHide the 2 CVE records in this change: Product added: fortisase named as affected from fortinet	fortinet	not named as affected at publication, now names fortisase	Time to revision 217 to 378 days
2026-06-23	CVE-2025-25250	same vendor as the line above	same change as the line above	Time to revision 378 days
2026-06-23	CVE-2025-54821	same vendor as the line above	same change as the line above	Time to revision 217 days
Tue 9 Jun 2026· 1 change
2026-06-09	CVE-2026-24858	fortinet	not named as affected at publication, now names fortinac-f	Time to revision 133 days
Tue 12 May 2026· 1 change
2026-05-12	CVE-2026-25836	fortinet	not named as affected at publication, now names fortisandbox paas	Time to revision 63 days
Wed 28 Jan 2026· 2 changes
2026-01-28	CVE-2026-24858Show all 2 products in this change: Product added: 2 products named as affected in CVE-2026-24858Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2026-24858	fortinet	not named as affected at publication, now names fortiproxy and 1 more	Time to revision 1 days
2026-01-28	CVE-2026-24858	same vendor as the line above	not named as affected at publication, now names fortiproxy	Time to revision 1 days
2026-01-28	CVE-2026-24858	same vendor as the line above	not named as affected at publication, now names fortiweb	Time to revision 1 days
Tue 27 Jan 2026· 2 changes
2026-01-27	CVE-2024-50571Show all 2 products in this change: Product added: 2 products named as affected in CVE-2024-50571Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2024-50571	fortinet	not named as affected at publication, now names fortianalyzer cloud and 1 more	Time to revision 105 days
2026-01-27	CVE-2024-50571	same vendor as the line above	not named as affected at publication, now names fortianalyzer cloud	Time to revision 105 days
2026-01-27	CVE-2024-50571	same vendor as the line above	not named as affected at publication, now names fortimanager cloud	Time to revision 105 days
Wed 14 Jan 2026· 7 changes
2026-01-14	CVE-2024-54026	fortinet	not named as affected at publication, now names fortisandbox cloud	Time to revision 309 days
2026-01-14	CVE-2023-41842	fortinet	not named as affected at publication, now names fortianalyzer-bigdata	Time to revision 673 days
2026-01-142 commits	Show all 3 CVE records in this change: Product added: fortimanager cloud named as affected from fortinetHide the 3 CVE records in this change: Product added: fortimanager cloud named as affected from fortinet	fortinet	not named as affected at publication, now names fortimanager cloudBranches and original-value intervals are stated on each row.	Time to revision 92 to 365 days
2026-01-14	CVE-2024-48884	same vendor as the line above	same change as the line above	Time to revision 365 days
2026-01-14	CVE-2024-50566	same vendor as the line above	same change as the line above	Time to revision 365 days
2026-01-14	CVE-2024-47569	same vendor as the line above	same change as the line above	Time to revision 92 days
2026-01-14	Show all 2 CVE records in this change: Product added: fortisase named as affected from fortinetHide the 2 CVE records in this change: Product added: fortisase named as affected from fortinet	fortinet	not named as affected at publication, now names fortisase	Time to revision 92 days
2026-01-14	CVE-2025-31366	same vendor as the line above	same change as the line above	Time to revision 92 days
2026-01-14	CVE-2025-47890	same vendor as the line above	same change as the line above	Time to revision 92 days

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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

What this page cannot see

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 →

Paste your closed CVE tickets and see which of these changes hit them →