Every change, newest first
| 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. |
|---|---|---|---|---|---|
| Fri 14 Aug 2026· 1 record change | |||||
| 2026-08-14 | Ransomware use confirmed | CVE-2019-5591 | FortinetFortiOS CISA KEV | stated at publication Unknown, now states Known | Days to revision at least 534 |
| Wed 12 Aug 2026· 7 record changes | |||||
| 2026-08-12 | Affected range extended | CVE-2023-42787 | fortinetfortianalyzer | 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 | Affected range extended | CVE-2023-42787 | fortinetfortianalyzer | 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 | Affected range extended | CVE-2023-42787 | fortinetfortimanager | 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 | Affected range extended | CVE-2023-42787 | fortinetfortimanager | 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 | Product added | CVE-2025-61848 | not named as affected at publication, now names fortianalyzer-bigdata | Days to revision 120 | |
| 2026-08-12 | Product added | CVE-2023-42787 | not named as affected at publication, now names fortianalyzer cloud | Days to revision 1,037 | |
| 2026-08-12 | Product added | CVE-2023-42787 | not named as affected at publication, now names fortianalyzer-bigdata | Days to revision 1,037 | |
| Mon 27 Jul 2026· 1 record change | |||||
| 2026-07-27 | Added to CISA KEV | CVE-2025-68686 | FortinetFortiOS CISA KEV | fix due 2026-08-10 | Not applicable: Added to CISA KEV has no earlier value |
| Thu 16 Jul 2026· 3 record changes | |||||
| 2026-07-16 | Added to CISA KEV | CVE-2026-25089 | FortinetFortiSandbox CISA KEV | fix due 2026-07-19 | Not applicable: Added to CISA KEV has no earlier value |
| 2026-07-16 | Added to CISA KEV | CVE-2026-39808 | FortinetFortiSandbox CISA KEV | fix due 2026-07-19 | Not applicable: Added to CISA KEV has no earlier value |
| 2026-07-16 | Affected range extended | 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· 17 record changes | |||||
| 2026-07-08 | Affected range extended | CVE-2024-33503 | fortinetfortimanager | stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0. | Days to revision 540 |
| 2026-07-08 | Affected range extended | 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 | Affected range extended | CVE-2024-45331 | fortinetfortimanager | stated at publication 7.0.13, now states 7.0.16Release branch starts at 7.0.0. | Days to revision 538 |
| 2026-07-08 | Affected range extended | CVE-2025-47890 | 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 | Affected range extended | CVE-2025-47890 | 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 | Affected range extended | CVE-2025-31366 | 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 | Affected range extended | CVE-2025-31366 | 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 | Affected range extended | CVE-2025-47890 | 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 | Affected range extended | 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 | Affected range extended | CVE-2025-47890 | 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 | Affected range extended | CVE-2025-31366 | 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 | Affected range extended | CVE-2025-31366 | 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 | Product added | CVE-2024-33503 | not named as affected at publication, now names fortimanager cloud | Days to revision 540 | |
| 2026-07-08 | Product added | CVE-2024-35276 | not named as affected at publication, now names fortianalyzer cloud | Days to revision 540 | |
| 2026-07-08 | Product added | CVE-2024-35276 | not named as affected at publication, now names fortimanager cloud | Days to revision 540 | |
| 2026-07-08 | Product added | CVE-2024-45331 | not named as affected at publication, now names fortianalyzer cloud | Days to revision 538 | |
| 2026-07-08 | Product added | CVE-2023-42789 | not named as affected at publication, now names fortisase | Days to revision 848 | |
| Tue 23 Jun 2026· 7 record changes | |||||
| 2026-06-23 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 |
| 2026-06-23 | Product added | CVE-2025-25250 | not named as affected at publication, now names fortisase | Days to revision 378 | |
| 2026-06-23 | Product added | CVE-2025-54821 | not named as affected at publication, now names fortisase | Days to revision 217 | |
| Fri 12 Jun 2026· 3 record changes | |||||
| 2026-06-12 | Affected range extended | CVE-2023-45583 | 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 | Affected range extended | 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 |
| 2026-06-12 | Affected range extended | CVE-2023-36640 | fortinetfortios | stated at publication 6.2.16, now states 6.2.17Release branch starts at 6.2.0. | Days to revision 759 |
| Tue 9 Jun 2026· 7 record changes | |||||
| 2026-06-09 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 |
| 2026-06-09 | Product added | CVE-2026-24858 | not named as affected at publication, now names fortinac-f | Days to revision 133 | |
| Tue 26 May 2026· 1 record change | |||||
| 2026-05-26 | Affected range extended | 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· 2 record changes | |||||
| 2026-05-12 | Affected range extended | 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 |
| 2026-05-12 | Product added | CVE-2026-25836 | not named as affected at publication, now names fortisandbox paas | Days to revision 63 | |
| Mon 13 Apr 2026· 1 record change | |||||
| 2026-04-13 | Added to CISA KEV | CVE-2026-21643 | FortinetFortiClient EMS CISA KEV | fix due 2026-04-16 | Not applicable: Added to CISA KEV has no earlier value |
| Mon 6 Apr 2026· 1 record change | |||||
| 2026-04-06 | Added to CISA KEV | CVE-2026-35616 | FortinetFortiClient EMS CISA KEV | fix due 2026-04-09 | Not applicable: Added to CISA KEV has no earlier value |
| Tue 10 Feb 2026· 2 record changes | |||||
| 2026-02-10 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 28 Jan 2026· 2 record changes | |||||
| 2026-01-28 | Product added | CVE-2026-24858 | not named as affected at publication, now names fortiproxy | Days to revision 1 | |
| 2026-01-28 | Product added | CVE-2026-24858 | not named as affected at publication, now names fortiweb | Days to revision 1 | |
| Tue 27 Jan 2026· 3 record changes | |||||
| 2026-01-27 | Added to CISA KEV | CVE-2026-24858 | FortinetMultiple Products CISA KEV | fix due 2026-01-30 | Not applicable: Added to CISA KEV has no earlier value |
| 2026-01-27 | Product added | CVE-2024-50571 | not named as affected at publication, now names fortianalyzer cloud | Days to revision 105 | |
| 2026-01-27 | Product added | CVE-2024-50571 | not named as affected at publication, now names fortimanager cloud | Days to revision 105 | |
| Wed 14 Jan 2026· 40 record changes | |||||
| 2026-01-14 | Affected range extended | CVE-2023-47541 | fortinetfortisandbox | stated at publication 4.0.5, now states 4.0.6Release branch starts at 4.0.0. | Days to revision 645 |
| 2026-01-14 | Affected range extended | 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-14 | Affected range extended | CVE-2023-41836 | fortinetfortisandbox | stated at publication 4.0.4, now states 4.0.6Release branch starts at 4.0.0. | Days to revision 824 |
| 2026-01-14 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | 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 | Affected range extended | CVE-2023-45587 | fortinetfortisandbox | stated at publication 4.0.4, now states 4.0.6Release branch starts at 4.0.0. | Days to revision 763 |
| 2026-01-14 | Affected range extended | CVE-2023-41844 | fortinetfortisandbox | stated at publication 4.0.4, now states 4.0.6Release branch starts at 4.0.0. | Days to revision 763 |
| 2026-01-14 | Affected range extended | CVE-2023-41842 | fortinetfortianalyzer | stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0. | Days to revision 673 |
| 2026-01-14 | Affected range extended | CVE-2023-41842 | fortinetfortianalyzer | stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0. | Days to revision 673 |
| 2026-01-14 | Affected range extended | CVE-2023-41842 | fortinetfortimanager | stated at publication 6.2.12, now states 6.2.13Release branch starts at 6.2.0. | Days to revision 673 |
| 2026-01-14 | Affected range extended | CVE-2023-41842 | fortinetfortimanager | stated at publication 6.4.14, now states 6.4.15Release branch starts at 6.4.0. | Days to revision 673 |
| 2026-01-14 | Affected range extended | CVE-2024-31487 | fortinetfortisandbox | stated at publication 4.0.5, now states 4.0.6Release branch starts at 4.0.0. | Days to revision 645 |
| 2026-01-14 | Affected range extended | CVE-2023-47540 | fortinetfortisandbox | stated at publication 4.0.5, now states 4.0.6Release branch starts at 4.0.0. | Days to revision 645 |
| 2026-01-14 | Affected range extended | CVE-2024-31490 | fortinetfortisandbox | stated at publication 4.0.5, now states 4.0.6Release branch starts at 4.0.0. | Days to revision 491 |
| 2026-01-14 | Affected range extended | 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 | Affected range extended | 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-14 | Affected range extended | CVE-2025-57740 | fortinetfortios | stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | CVE-2025-57740 | fortinetfortiproxy | stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | CVE-2024-26008 | fortinetfortios | stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | CVE-2024-26008 | fortinetfortiproxy | stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | 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 | Affected range extended | CVE-2025-54822 | fortinetfortiproxy | stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | 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 | Affected range extended | CVE-2024-40588 | fortinetfortimail | stated at publication 7.2.8, now states 7.2.9Release branch starts at 7.2.0. | Days to revision 155 |
| 2026-01-14 | Affected range extended | CVE-2025-53609 | fortinetfortiweb | stated at publication 7.0.11, now states 7.0.12Release branch starts at 7.0.2. | Days to revision 127 |
| 2026-01-14 | Affected range extended | CVE-2025-22862 | fortinetfortios | stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.6. | Days to revision 104 |
| 2026-01-14 | Affected range extended | CVE-2025-22862 | fortinetfortiproxy | stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.5. | Days to revision 104 |
| 2026-01-14 | Affected range extended | CVE-2025-58903 | fortinetfortios | stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | 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 | Affected range extended | CVE-2025-25253 | fortinetfortios | stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | CVE-2025-25253 | fortinetfortiproxy | stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | CVE-2023-46718 | fortinetfortios | stated at publication 7.0.17, now states 7.0.18Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | CVE-2023-46718 | fortinetfortiproxy | stated at publication 7.0.21, now states 7.0.22Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | 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 |
| 2026-01-14 | Affected range extended | CVE-2024-47569 | fortinetfortiweb | stated at publication 7.0.11, now states 7.0.12Release branch starts at 7.0.0. | Days to revision 92 |
| 2026-01-14 | Affected range extended | CVE-2025-54972 | fortinetfortimail | stated at publication 7.2.8, now states 7.2.9Release branch starts at 7.2.0. | Days to revision 57 |
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.
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 →