Affected range extended

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

92 changes · newest first · grouped by dayCSV JSON RSS

Counted changes of "Affected range extended" from fortinet, 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· 4 changes
2026-08-12	CVE-2023-42787Show all 2 products in this change: Affected range extended: 6.2.12 → 6.2.13 in CVE-2023-42787Hide the 2 products in this change: Affected range extended: 6.2.12 → 6.2.13 in CVE-2023-42787	fortinet2 products	stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0.	Time to revision 1,037 days
2026-08-12	CVE-2023-42787	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.0.	Time to revision 1,037 days
2026-08-12	CVE-2023-42787	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.0.	Time to revision 1,037 days
2026-08-12	CVE-2023-42787Show all 2 products in this change: Affected range extended: 6.4.13 → 6.4.15 in CVE-2023-42787Hide the 2 products in this change: Affected range extended: 6.4.13 → 6.4.15 in CVE-2023-42787	fortinet2 products	stated at publication 6.4.13, now states 6.4.15Release branch starts at 6.4.0.	Time to revision 1,037 days
2026-08-12	CVE-2023-42787	same vendor as the line above	same change as the line aboveRelease branch starts at 6.4.0.	Time to revision 1,037 days
2026-08-12	CVE-2023-42787	same vendor as the line above	same change as the line aboveRelease branch starts at 6.4.0.	Time to revision 1,037 days
Thu 16 Jul 2026· 1 change
2026-07-16	CVE-2026-59840	fortinetfortios	stated at publication 7.6.2, now states 7.6.3Release branch starts at 7.6.0.	Time to revision 2 days
Wed 8 Jul 2026· 12 changes
2026-07-08	Show all 2 CVE records in this change: Affected range extended: 7.0.13 → 7.0.16 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.0.13 → 7.0.16 from fortinet	fortinetfortimanager	stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0.	Time to revision 538 to 540 days
2026-07-08	CVE-2024-33503	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 540 days
2026-07-08	CVE-2024-45331	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 538 days
2026-07-08	CVE-2024-45331	fortinetfortianalyzer	stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0.	Time to revision 538 days
2026-07-08	Show all 2 CVE records in this change: Affected range extended: 7.2.12 → 7.2.13 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.2.12 → 7.2.13 from fortinet	fortinetfortios	stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0.	Time to revision 267 days
2026-07-08	CVE-2025-47890	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Time to revision 267 days
2026-07-08	CVE-2025-31366	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Time to revision 267 days
2026-07-08	Show all 2 CVE records in this change: Affected range extended: 7.2.15 → 7.2.16 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.2.15 → 7.2.16 from fortinet	fortinetfortiproxy	stated at publication 7.2.15, now states 7.2.16Release branch starts at 7.2.0.	Time to revision 267 days
2026-07-08	CVE-2025-47890	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Time to revision 267 days
2026-07-08	CVE-2025-31366	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Time to revision 267 days
2026-07-08	Show all 2 CVE records in this change: Affected range extended: 7.0.17 → 7.0.19 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.0.17 → 7.0.19 from fortinet	fortinetfortios	stated at publication 7.0.17, now states 7.0.19Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.	Time to revision 92 days
2026-07-08	CVE-2025-47890	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.	Time to revision 92 days
2026-07-08	CVE-2025-31366	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.	Time to revision 92 days
2026-07-08	CVE-2025-47890	fortinetfortiproxy	stated at publication 7.4.11, now states 7.4.14Release branch starts at 7.4.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.	Time to revision 92 days
2026-07-08	Show all 2 CVE records in this change: Affected range extended: 7.0.21 → 7.0.23 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.0.21 → 7.0.23 from fortinet	fortinetfortiproxy	stated at publication 7.0.21, now states 7.0.23Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.	Time to revision 92 days
2026-07-08	CVE-2025-47890	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.	Time to revision 92 days
2026-07-08	CVE-2025-31366	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-07-08.	Time to revision 92 days
Tue 23 Jun 2026· 5 changes
2026-06-23	CVE-2025-25250	fortinetfortios	stated at publication 7.2.11, now states 7.2.13Release branch starts at 7.2.0.	Time to revision 378 days
2026-06-23	CVE-2025-25250	fortinetfortios	stated at publication 7.0.17, now states 7.0.19Release branch starts at 7.0.0.	Time to revision 378 days
2026-06-23	CVE-2025-54821	fortinetfortios	stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0.	Time to revision 217 days
2026-06-23	CVE-2025-54821	fortinetfortios	stated at publication 7.4.9, now states 7.4.11Release branch starts at 7.4.0.	Time to revision 217 days
2026-06-23	CVE-2025-54821	fortinetfortios	stated at publication 7.0.18, now states 7.0.19Release branch starts at 7.0.0.	Time to revision 217 days
Fri 12 Jun 2026· 3 changes
2026-06-12	Show all 2 CVE records in this change: Affected range extended: 6.2.16 → 6.2.17 from fortinetHide the 2 CVE records in this change: Affected range extended: 6.2.16 → 6.2.17 from fortinet	fortinetfortios	stated at publication 6.2.16, now states 6.2.17Release branch starts at 6.2.0.	Time to revision 759 days
2026-06-12	CVE-2023-45583	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.0.	Time to revision 759 days
2026-06-12	CVE-2023-36640	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.0.	Time to revision 759 days
2026-06-12	CVE-2023-45583	fortinetfortios	stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0.	Time to revision 759 days
Tue 9 Jun 2026· 6 changes
2026-06-09	CVE-2025-31514	fortinetfortios	stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0.	Time to revision 238 days
2026-06-09	CVE-2025-31514	fortinetfortios	stated at publication 7.4.9, now states 7.4.11Release branch starts at 7.4.0.	Time to revision 238 days
2026-06-09	CVE-2025-31514	fortinetfortiproxy	stated at publication 7.2.15, now states 7.2.16Release branch starts at 7.2.0.	Time to revision 238 days
2026-06-09	CVE-2025-31514	fortinetfortios	stated at publication 7.0.17, now states 7.0.19Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-06-09.	Time to revision 92 days
2026-06-09	CVE-2025-31514	fortinetfortiproxy	stated at publication 7.4.11, now states 7.4.13Release branch starts at 7.4.0.Original value first replaced 2026-01-14; this value first seen 2026-06-09.	Time to revision 92 days
2026-06-09	CVE-2025-31514	fortinetfortiproxy	stated at publication 7.0.21, now states 7.0.23Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-06-09.	Time to revision 92 days
Tue 26 May 2026· 1 change
2026-05-26	CVE-2025-68648	fortinetfortianalyzer cloud	stated at publication 7.0.15, now states 7.0.16Release branch starts at 7.0.1.	Time to revision 77 days
Tue 12 May 2026· 1 change
2026-05-12	CVE-2025-62631	fortinetfortios	stated at publication 7.2.11, now states 7.2.13Release branch starts at 7.2.0.	Time to revision 154 days
Tue 10 Feb 2026· 2 changes
2026-02-10	CVE-2024-47569	fortinetfortiproxy	stated at publication 7.0.21, now states 7.0.23Release branch starts at 7.0.0.Original value first replaced 2026-01-14; this value first seen 2026-02-10.	Time to revision 92 days
2026-02-10	CVE-2025-62631	fortinetfortios	stated at publication 7.0.18, now states 7.0.19Release branch starts at 7.0.0.	Time to revision 63 days
Wed 4 Feb 2026· 2 changes
2026-02-04	CVE-2024-45326	fortinetfortideceptor	stated at publication 5.2.1, now states 5.2.2Release branch starts at 5.2.0.	Time to revision 386 days
2026-02-04	CVE-2024-45326	fortinetfortideceptor	stated at publication 5.3.3, now states 5.3.4Release branch starts at 5.3.0.	Time to revision 386 days
Wed 14 Jan 2026· 40 changes
2026-01-142 commits	Show all 4 CVE records in this change: Affected range extended: 4.0.5 → 4.0.6 from fortinetHide the 4 CVE records in this change: Affected range extended: 4.0.5 → 4.0.6 from fortinet	fortinetfortisandbox	stated at publication 4.0.5, now states 4.0.6Branches and original-value intervals are stated on each row.	Time to revision 491 to 645 days
2026-01-14	CVE-2023-47541	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Time to revision 645 days
2026-01-14	CVE-2024-31487	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Time to revision 645 days
2026-01-14	CVE-2023-47540	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Time to revision 645 days
2026-01-14	CVE-2024-31490	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Time to revision 491 days
2026-01-14	CVE-2023-26210	fortinetfortiadc	stated at publication 7.0.5, now states 7.0.6Release branch starts at 7.0.0.	Time to revision 946 days
2026-01-142 commits	Show all 3 CVE records in this change: Affected range extended: 4.0.4 → 4.0.6 from fortinetHide the 3 CVE records in this change: Affected range extended: 4.0.4 → 4.0.6 from fortinet	fortinetfortisandbox	stated at publication 4.0.4, now states 4.0.6Branches and original-value intervals are stated on each row.	Time to revision 763 to 824 days
2026-01-14	CVE-2023-41836	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Time to revision 824 days
2026-01-14	CVE-2023-45587	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Time to revision 763 days
2026-01-14	CVE-2023-41844	same vendor as the line above	same change as the line aboveRelease branch starts at 4.0.0.	Time to revision 763 days
2026-01-14	CVE-2023-40721	fortinetfortios	stated at publication 6.2.16, now states 6.2.17Release branch starts at 6.2.0.	Time to revision 337 days
2026-01-14	CVE-2023-40721	fortinetfortios	stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0.	Time to revision 337 days
2026-01-14	CVE-2023-29175	fortinetfortios	stated at publication 6.2.15, now states 6.2.17Release branch starts at 6.2.0.	Time to revision 946 days
2026-01-14	CVE-2023-29175	fortinetfortios	stated at publication 6.4.13, now states 6.4.16Release branch starts at 6.4.0.	Time to revision 946 days
2026-01-14	CVE-2023-29175	fortinetfortios	stated at publication 6.0.17, now states 6.0.18Release branch starts at 6.0.0.	Time to revision 946 days
2026-01-14	CVE-2023-29175	fortinetfortiproxy	stated at publication 2.0.12, now states 2.0.14Release branch starts at 2.0.0.	Time to revision 946 days
2026-01-14	CVE-2023-41842Show all 2 products in this change: Affected range extended: 6.2.12 → 6.2.13 in CVE-2023-41842Hide the 2 products in this change: Affected range extended: 6.2.12 → 6.2.13 in CVE-2023-41842	fortinet2 products	stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0.	Time to revision 673 days
2026-01-14	CVE-2023-41842	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.0.	Time to revision 673 days
2026-01-14	CVE-2023-41842	same vendor as the line above	same change as the line aboveRelease branch starts at 6.2.0.	Time to revision 673 days
2026-01-14	CVE-2023-41842Show all 2 products in this change: Affected range extended: 6.4.14 → 6.4.15 in CVE-2023-41842Hide the 2 products in this change: Affected range extended: 6.4.14 → 6.4.15 in CVE-2023-41842	fortinet2 products	stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0.	Time to revision 673 days
2026-01-14	CVE-2023-41842	same vendor as the line above	same change as the line aboveRelease branch starts at 6.4.0.	Time to revision 673 days
2026-01-14	CVE-2023-41842	same vendor as the line above	same change as the line aboveRelease branch starts at 6.4.0.	Time to revision 673 days
2026-01-14	CVE-2024-48885	fortinetfortiweb	stated at publication 7.2.10, now states 7.2.12Release branch starts at 7.2.0.	Time to revision 363 days
2026-01-14	CVE-2024-48885	fortinetfortiweb	stated at publication 7.0.10, now states 7.0.12Release branch starts at 7.0.0.	Time to revision 363 days
2026-01-142 commits	Show all 6 CVE records in this change: Affected range extended: 7.0.17 → 7.0.18 from fortinetHide the 6 CVE records in this change: Affected range extended: 7.0.17 → 7.0.18 from fortinet	fortinetfortios	stated at publication 7.0.17, now states 7.0.182 release branches. Branches and original-value intervals are stated on each row.	Time to revision 92 to 104 days
2026-01-14	CVE-2025-57740	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2024-26008	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2025-22862	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.6.	Time to revision 104 days
2026-01-14	CVE-2025-58903	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2025-25253	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2023-46718	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-142 commits	Show all 6 CVE records in this change: Affected range extended: 7.0.21 → 7.0.22 from fortinetHide the 6 CVE records in this change: Affected range extended: 7.0.21 → 7.0.22 from fortinet	fortinetfortiproxy	stated at publication 7.0.21, now states 7.0.222 release branches. Branches and original-value intervals are stated on each row.	Time to revision 92 to 104 days
2026-01-14	CVE-2025-57740	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2024-26008	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2025-54822	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2025-22862	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.5.	Time to revision 104 days
2026-01-14	CVE-2025-25253	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2023-46718	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2025-53845	fortinetfortianalyzer	stated at publication 7.0.14, now states 7.0.15Release branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2024-46669	fortinetfortios	stated at publication 7.2.10, now states 7.2.11Release branch starts at 7.2.0.	Time to revision 365 days
2026-01-14	Show all 2 CVE records in this change: Affected range extended: 7.2.8 → 7.2.9 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.2.8 → 7.2.9 from fortinet	fortinetfortimail	stated at publication 7.2.8, now states 7.2.9Release branch starts at 7.2.0.	Time to revision 57 to 155 days
2026-01-14	CVE-2024-40588	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Time to revision 155 days
2026-01-14	CVE-2025-54972	same vendor as the line above	same change as the line aboveRelease branch starts at 7.2.0.	Time to revision 57 days
2026-01-14	Show all 2 CVE records in this change: Affected range extended: 7.0.11 → 7.0.12 from fortinetHide the 2 CVE records in this change: Affected range extended: 7.0.11 → 7.0.12 from fortinet	fortinetfortiweb	stated at publication 7.0.11, now states 7.0.122 release branches. Branches and original-value intervals are stated on each row.	Time to revision 92 to 127 days
2026-01-14	CVE-2025-53609	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.2.	Time to revision 127 days
2026-01-14	CVE-2024-47569	same vendor as the line above	same change as the line aboveRelease branch starts at 7.0.0.	Time to revision 92 days
2026-01-14	CVE-2025-58324	fortinetfortisiem	stated at publication 7.1.8, now states 7.1.9Release branch starts at 7.1.0.	Time to revision 92 days
2026-01-14	CVE-2024-47569	fortinetfortiweb	stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.0.	Time to revision 92 days
Fri 19 Dec 2025· 1 change
2025-12-19	CVE-2023-44247	fortinetfortios	stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0.	Time to revision 584 days
Thu 11 Dec 2025· 1 change
2025-12-11	CVE-2025-59923	fortinetfortiauthenticator	stated at publication 6.6.4, now states 6.6.6Release branch starts at 6.6.0.	Time to revision 2 days
Wed 10 Dec 2025· 1 change
2025-12-10	CVE-2025-64471	fortinetfortiweb	stated at publication 7.6.4, now states 7.6.5Release branch starts at 7.6.0.	Time to revision 1 days
Tue 18 Nov 2025· 3 changes
2025-11-18	CVE-2024-32122	fortinetfortios	stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.0.	Time to revision 224 days
2025-11-18	CVE-2024-32122	fortinetfortios	stated at publication 7.4.7, now states 7.4.8Release branch starts at 7.4.0.	Time to revision 224 days
2025-11-18	CVE-2024-32122	fortinetfortios	stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0.	Time to revision 224 days
Mon 3 Nov 2025· 1 change
2025-11-03	CVE-2025-24477	fortinetfortios	stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.4.	Time to revision 111 days
Thu 16 Oct 2025· 1 change
2025-10-16	CVE-2025-25255	fortinetfortiproxy	stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.1.	Time to revision 2 days
Fri 18 Oct 2024· 6 changes
2024-10-18	CVE-2023-28002	fortinetfortiproxy	stated at publication 2.0.13, now states 2.0.14Release branch starts at 2.0.0.	Time to revision 339 days
2024-10-18	CVE-2023-28002	fortinetfortiproxy	stated at publication 7.2.7, now states 7.2.8Release branch starts at 7.2.0.	Time to revision 339 days
2024-10-18	CVE-2023-28002	fortinetfortiproxy	stated at publication 7.0.13, now states 7.0.19Release branch starts at 7.0.0.	Time to revision 339 days
2024-10-18	CVE-2023-28002	fortinetfortios	stated at publication 6.2.15, now states 6.2.16Release branch starts at 6.2.0.	Time to revision 339 days
2024-10-18	CVE-2023-28002	fortinetfortios	stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0.	Time to revision 339 days
2024-10-18	CVE-2023-28002	fortinetfortios	stated at publication 6.0.17, now states 6.0.18Release branch starts at 6.0.0.	Time to revision 339 days
Tue 21 May 2024· 1 change
2024-05-21	CVE-2023-47537	fortinetfortios	stated at publication 7.0.14, now states 7.0.15Release branch starts at 7.0.0.	Time to revision 96 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

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

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 →