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. |
|---|---|---|---|---|---|
| Mon 24 Aug 2026· 1 change | |||||
| 2026-08-24 | CVSS base score changed | CVE-2023-50176 | whole record fortinet | stated at publication 7.1, now states 4.0CVSS v3.1 · base scoreHighMedium | Time to revision 650 days |
| Wed 12 Aug 2026· 7 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. | Time to revision 1,037 days |
| 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. | Time to revision 1,037 days |
| 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. | Time to revision 1,037 days |
| 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. | Time to revision 1,037 days |
| 2026-08-12 | Product added | CVE-2025-61848 | not named as affected at publication, now names fortianalyzer-bigdata | Time to revision 120 days | |
| 2026-08-12 | Product added | CVE-2023-42787 | not named as affected at publication, now names fortianalyzer cloud | Time to revision 1,037 days | |
| 2026-08-12 | Product added | CVE-2023-42787 | not named as affected at publication, now names fortianalyzer-bigdata | Time to revision 1,037 days | |
| Tue 11 Aug 2026· 1 change | |||||
| 2026-08-11 | CVSS base score changed | CVE-2025-61848 | whole record fortinet | stated at publication 6.8, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 119 days |
| Thu 16 Jul 2026· 1 change | |||||
| 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. | Time to revision 2 days |
| Wed 8 Jul 2026· 17 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. | Time to revision 540 days |
| 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. | Time to revision 538 days |
| 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. | Time to revision 538 days |
| 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. | Time to revision 267 days |
| 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. | Time to revision 267 days |
| 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. | Time to revision 267 days |
| 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. | Time to revision 267 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 2026-07-08 | Product added | CVE-2024-33503 | not named as affected at publication, now names fortimanager cloud | Time to revision 540 days | |
| 2026-07-08 | Product added | CVE-2024-35276 | not named as affected at publication, now names fortianalyzer cloud | Time to revision 540 days | |
| 2026-07-08 | Product added | CVE-2024-35276 | not named as affected at publication, now names fortimanager cloud | Time to revision 540 days | |
| 2026-07-08 | Product added | CVE-2024-45331 | not named as affected at publication, now names fortianalyzer cloud | Time to revision 538 days | |
| 2026-07-08 | Product added | CVE-2023-42789 | not named as affected at publication, now names fortisase | Time to revision 848 days | |
| Tue 23 Jun 2026· 7 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. | Time to revision 378 days |
| 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. | Time to revision 378 days |
| 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. | Time to revision 217 days |
| 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. | Time to revision 217 days |
| 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. | Time to revision 217 days |
| 2026-06-23 | Product added | CVE-2025-25250 | not named as affected at publication, now names fortisase | Time to revision 378 days | |
| 2026-06-23 | Product added | CVE-2025-54821 | not named as affected at publication, now names fortisase | Time to revision 217 days | |
| Fri 12 Jun 2026· 3 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. | Time to revision 759 days |
| 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. | Time to revision 759 days |
| 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. | Time to revision 759 days |
| Tue 9 Jun 2026· 7 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. | Time to revision 238 days |
| 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. | Time to revision 238 days |
| 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. | Time to revision 238 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 2026-06-09 | Product added | CVE-2026-24858 | not named as affected at publication, now names fortinac-f | Time to revision 133 days | |
| Tue 26 May 2026· 1 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. | Time to revision 77 days |
| Tue 12 May 2026· 2 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. | Time to revision 154 days |
| 2026-05-12 | Product added | CVE-2026-25836 | not named as affected at publication, now names fortisandbox paas | Time to revision 63 days | |
| Tue 10 Feb 2026· 2 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. | Time to revision 92 days |
| 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. | Time to revision 63 days |
| Wed 4 Feb 2026· 2 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. | Time to revision 386 days |
| 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. | Time to revision 386 days |
| Wed 28 Jan 2026· 2 changes | |||||
| 2026-01-28 | Product added | CVE-2026-24858 | not named as affected at publication, now names fortiproxy | Time to revision 1 days | |
| 2026-01-28 | Product added | CVE-2026-24858 | not named as affected at publication, now names fortiweb | Time to revision 1 days | |
| Tue 27 Jan 2026· 2 changes | |||||
| 2026-01-27 | Product added | CVE-2024-50571 | not named as affected at publication, now names fortianalyzer cloud | Time to revision 105 days | |
| 2026-01-27 | Product added | CVE-2024-50571 | not named as affected at publication, now names fortimanager cloud | Time to revision 105 days | |
| Wed 14 Jan 2026· 45 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. | Time to revision 645 days |
| 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. | Time to revision 946 days |
| 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. | Time to revision 824 days |
| 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. | Time to revision 337 days |
| 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. | Time to revision 337 days |
| 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. | Time to revision 946 days |
| 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. | Time to revision 946 days |
| 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. | Time to revision 946 days |
| 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. | Time to revision 946 days |
| 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. | Time to revision 763 days |
| 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. | Time to revision 763 days |
| 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. | Time to revision 673 days |
| 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. | Time to revision 673 days |
| 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. | Time to revision 673 days |
| 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. | Time to revision 673 days |
| 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. | Time to revision 645 days |
| 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. | Time to revision 645 days |
| 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. | Time to revision 491 days |
| 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. | Time to revision 363 days |
| 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. | Time to revision 363 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 365 days |
| 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. | Time to revision 155 days |
| 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. | Time to revision 127 days |
| 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. | Time to revision 104 days |
| 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. | Time to revision 104 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 92 days |
| 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. | Time to revision 57 days |
| 2026-01-14 | Product added | CVE-2024-54026 | not named as affected at publication, now names fortisandbox cloud | Time to revision 309 days | |
| 2026-01-14 | Product added | CVE-2023-41842 | not named as affected at publication, now names fortianalyzer-bigdata | Time to revision 673 days | |
| 2026-01-14 | Product added | CVE-2024-48884 | not named as affected at publication, now names fortimanager cloud | Time to revision 365 days | |
| 2026-01-14 | Product added | CVE-2024-50566 | not named as affected at publication, now names fortimanager cloud | Time to revision 365 days | |
| 2026-01-14 | Product added | CVE-2025-31366 | not named as affected at publication, now names fortisase | Time to revision 92 days | |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or 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 →