Affected range extended
| 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 record changes | ||||
| 2026-08-12 | CVE-2023-42787 | fortinet2 products | stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0. | Days to revision 1,037 |
| 2026-08-12 | CVE-2023-42787 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.0. | Days to revision 1,037 |
| 2026-08-12 | CVE-2023-42787 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.0. | Days to revision 1,037 |
| 2026-08-12 | CVE-2023-42787 | fortinet2 products | stated at publication 6.4.13, now states 6.4.15Release branch starts at 6.4.0. | Days to revision 1,037 |
| 2026-08-12 | CVE-2023-42787 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.4.0. | Days to revision 1,037 |
| 2026-08-12 | CVE-2023-42787 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.4.0. | Days to revision 1,037 |
| Thu 16 Jul 2026· 1 record 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. | Days to revision 2 |
| Wed 8 Jul 2026· 12 record changes | ||||
| 2026-07-08 | fortinetfortimanager | stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0. | Days to revision 538 to 540 | |
| 2026-07-08 | CVE-2024-33503 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 540 |
| 2026-07-08 | CVE-2024-45331 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 538 |
| 2026-07-08 | CVE-2024-45331 | fortinetfortianalyzer | stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0. | Days to revision 538 |
| 2026-07-08 | fortinetfortios | stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0. | Days to revision 267 | |
| 2026-07-08 | CVE-2025-47890 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.2.0. | Days to revision 267 |
| 2026-07-08 | CVE-2025-31366 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.2.0. | Days to revision 267 |
| 2026-07-08 | fortinetfortiproxy | stated at publication 7.2.15, now states 7.2.16Release branch starts at 7.2.0. | Days to revision 267 | |
| 2026-07-08 | CVE-2025-47890 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.2.0. | Days to revision 267 |
| 2026-07-08 | CVE-2025-31366 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.2.0. | Days to revision 267 |
| 2026-07-08 | 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. | Days to revision 92 | |
| 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. | Days to revision 92 |
| 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. | Days to revision 92 |
| 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. | Days to revision 92 |
| 2026-07-08 | 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. | Days to revision 92 | |
| 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. | Days to revision 92 |
| 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. | Days to revision 92 |
| Tue 23 Jun 2026· 5 record 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. | Days to revision 378 |
| 2026-06-23 | CVE-2025-25250 | fortinetfortios | stated at publication 7.0.17, now states 7.0.19Release branch starts at 7.0.0. | Days to revision 378 |
| 2026-06-23 | CVE-2025-54821 | fortinetfortios | stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0. | Days to revision 217 |
| 2026-06-23 | CVE-2025-54821 | fortinetfortios | stated at publication 7.4.9, now states 7.4.11Release branch starts at 7.4.0. | Days to revision 217 |
| 2026-06-23 | CVE-2025-54821 | fortinetfortios | stated at publication 7.0.18, now states 7.0.19Release branch starts at 7.0.0. | Days to revision 217 |
| Fri 12 Jun 2026· 3 record changes | ||||
| 2026-06-12 | fortinetfortios | stated at publication 6.2.16, now states 6.2.17Release branch starts at 6.2.0. | Days to revision 759 | |
| 2026-06-12 | CVE-2023-45583 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.0. | Days to revision 759 |
| 2026-06-12 | CVE-2023-36640 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.0. | Days to revision 759 |
| 2026-06-12 | CVE-2023-45583 | fortinetfortios | stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0. | Days to revision 759 |
| Tue 9 Jun 2026· 6 record 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. | Days to revision 238 |
| 2026-06-09 | CVE-2025-31514 | fortinetfortios | stated at publication 7.4.9, now states 7.4.11Release branch starts at 7.4.0. | Days to revision 238 |
| 2026-06-09 | CVE-2025-31514 | fortinetfortiproxy | stated at publication 7.2.15, now states 7.2.16Release branch starts at 7.2.0. | Days to revision 238 |
| 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. | Days to revision 92 |
| 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. | Days to revision 92 |
| 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. | Days to revision 92 |
| Tue 26 May 2026· 1 record 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. | Days to revision 77 |
| Tue 12 May 2026· 1 record 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. | Days to revision 154 |
| Tue 10 Feb 2026· 2 record 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. | Days to revision 92 |
| 2026-02-10 | CVE-2025-62631 | fortinetfortios | stated at publication 7.0.18, now states 7.0.19Release branch starts at 7.0.0. | Days to revision 63 |
| Wed 4 Feb 2026· 2 record 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. | Days to revision 386 |
| 2026-02-04 | CVE-2024-45326 | fortinetfortideceptor | stated at publication 5.3.3, now states 5.3.4Release branch starts at 5.3.0. | Days to revision 386 |
| Wed 14 Jan 2026· 40 record changes | ||||
| 2026-01-142 commits | fortinetfortisandbox | stated at publication 4.0.5, now states 4.0.6Branches and original-value intervals are stated on each row. | Days to revision 491 to 645 | |
| 2026-01-14 | CVE-2023-47541 | same vendor as the line above | same change as the line aboveRelease branch starts at 4.0.0. | Days to revision 645 |
| 2026-01-14 | CVE-2024-31487 | same vendor as the line above | same change as the line aboveRelease branch starts at 4.0.0. | Days to revision 645 |
| 2026-01-14 | CVE-2023-47540 | same vendor as the line above | same change as the line aboveRelease branch starts at 4.0.0. | Days to revision 645 |
| 2026-01-14 | CVE-2024-31490 | same vendor as the line above | same change as the line aboveRelease branch starts at 4.0.0. | Days to revision 491 |
| 2026-01-14 | CVE-2023-26210 | fortinetfortiadc | stated at publication 7.0.5, now states 7.0.6Release branch starts at 7.0.0. | Days to revision 946 |
| 2026-01-142 commits | fortinetfortisandbox | stated at publication 4.0.4, now states 4.0.6Branches and original-value intervals are stated on each row. | Days to revision 763 to 824 | |
| 2026-01-14 | CVE-2023-41836 | same vendor as the line above | same change as the line aboveRelease branch starts at 4.0.0. | Days to revision 824 |
| 2026-01-14 | CVE-2023-45587 | same vendor as the line above | same change as the line aboveRelease branch starts at 4.0.0. | Days to revision 763 |
| 2026-01-14 | CVE-2023-41844 | same vendor as the line above | same change as the line aboveRelease branch starts at 4.0.0. | Days to revision 763 |
| 2026-01-14 | CVE-2023-40721 | fortinetfortios | stated at publication 6.2.16, now states 6.2.17Release branch starts at 6.2.0. | Days to revision 337 |
| 2026-01-14 | CVE-2023-40721 | fortinetfortios | stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0. | Days to revision 337 |
| 2026-01-14 | CVE-2023-29175 | fortinetfortios | stated at publication 6.2.15, now states 6.2.17Release branch starts at 6.2.0. | Days to revision 946 |
| 2026-01-14 | CVE-2023-29175 | fortinetfortios | stated at publication 6.4.13, now states 6.4.16Release branch starts at 6.4.0. | Days to revision 946 |
| 2026-01-14 | CVE-2023-29175 | fortinetfortios | stated at publication 6.0.17, now states 6.0.18Release branch starts at 6.0.0. | Days to revision 946 |
| 2026-01-14 | CVE-2023-29175 | fortinetfortiproxy | stated at publication 2.0.12, now states 2.0.14Release branch starts at 2.0.0. | Days to revision 946 |
| 2026-01-14 | CVE-2023-41842 | fortinet2 products | stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0. | Days to revision 673 |
| 2026-01-14 | CVE-2023-41842 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.0. | Days to revision 673 |
| 2026-01-14 | CVE-2023-41842 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.0. | Days to revision 673 |
| 2026-01-14 | CVE-2023-41842 | fortinet2 products | stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0. | Days to revision 673 |
| 2026-01-14 | CVE-2023-41842 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.4.0. | Days to revision 673 |
| 2026-01-14 | CVE-2023-41842 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.4.0. | Days to revision 673 |
| 2026-01-14 | CVE-2024-48885 | fortinetfortiweb | stated at publication 7.2.10, now states 7.2.12Release branch starts at 7.2.0. | Days to revision 363 |
| 2026-01-14 | CVE-2024-48885 | fortinetfortiweb | stated at publication 7.0.10, now states 7.0.12Release branch starts at 7.0.0. | Days to revision 363 |
| 2026-01-142 commits | fortinetfortios | stated at publication 7.0.17, now states 7.0.182 release branches. Branches and original-value intervals are stated on each row. | Days to revision 92 to 104 | |
| 2026-01-14 | CVE-2025-57740 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2024-26008 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2025-22862 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.6. | Days to revision 104 |
| 2026-01-14 | CVE-2025-58903 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2025-25253 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2023-46718 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-142 commits | fortinetfortiproxy | stated at publication 7.0.21, now states 7.0.222 release branches. Branches and original-value intervals are stated on each row. | Days to revision 92 to 104 | |
| 2026-01-14 | CVE-2025-57740 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2024-26008 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2025-54822 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2025-22862 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.5. | Days to revision 104 |
| 2026-01-14 | CVE-2025-25253 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2023-46718 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2025-53845 | fortinetfortianalyzer | stated at publication 7.0.14, now states 7.0.15Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2024-46669 | fortinetfortios | stated at publication 7.2.10, now states 7.2.11Release branch starts at 7.2.0. | Days to revision 365 |
| 2026-01-14 | fortinetfortimail | stated at publication 7.2.8, now states 7.2.9Release branch starts at 7.2.0. | Days to revision 57 to 155 | |
| 2026-01-14 | CVE-2024-40588 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.2.0. | Days to revision 155 |
| 2026-01-14 | CVE-2025-54972 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.2.0. | Days to revision 57 |
| 2026-01-14 | fortinetfortiweb | stated at publication 7.0.11, now states 7.0.122 release branches. Branches and original-value intervals are stated on each row. | Days to revision 92 to 127 | |
| 2026-01-14 | CVE-2025-53609 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.2. | Days to revision 127 |
| 2026-01-14 | CVE-2024-47569 | same vendor as the line above | same change as the line aboveRelease branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | CVE-2025-58324 | fortinetfortisiem | stated at publication 7.1.8, now states 7.1.9Release branch starts at 7.1.0. | Days to revision 92 |
| 2026-01-14 | CVE-2024-47569 | fortinetfortiweb | stated at publication 7.2.11, now states 7.2.12Release branch starts at 7.2.0. | Days to revision 92 |
| Fri 19 Dec 2025· 1 record 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. | Days to revision 584 |
| Thu 11 Dec 2025· 1 record 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. | Days to revision 2 |
| Wed 10 Dec 2025· 1 record 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. | Days to revision 1 |
| Tue 18 Nov 2025· 3 record 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. | Days to revision 224 |
| 2025-11-18 | 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 | 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 |
| Mon 3 Nov 2025· 1 record 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. | Days to revision 111 |
| Thu 16 Oct 2025· 1 record 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. | Days to revision 2 |
| Fri 18 Oct 2024· 6 record 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. | Days to revision 339 |
| 2024-10-18 | 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 | 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 | 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 | 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 | 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 | 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 |
This kind is counted once per record, product and release branch, so one record that moved the boundary on four branches 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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →