Skip to content

Vendors

Fortinet

73records21productslast change2026-08-14RSSas of the 2026-09-07 snapshot

Rows per week, last 26 weeks

51 rows in the last 26 weeks, 0 in the week to 2026-09-070 this week

Rows, not records: one record that changed for four products is four rows and one record.

Choose a product · 21 products

21 of 21 products

Open the full product index. Counts beside products are records and are not added across products.

Every change, newest first

lines 1 to 20 of 69 · standing on 55 of 133 rows
Every counted change to a CVE or CISA KEV record naming Fortinet, newest first. A line standing for the same change across several records or products says how many and opens to every one.
Changed on, The day the commit that carried this change was read. Where the same change spans several days, the first and the last, never a midpoint. Not dated means no commit could be located for the row.ChangeCVEProductWhat the record says now
2025-04-07 to2026-08-14Ransomware use confirmedFortiOSstated at publication Unknown, now states Known
2026-08-14Ransomware use confirmedCVE-2019-5591FortiOSstated at publication Unknown, now states Known
2025-07-14Ransomware use confirmedCVE-2019-6693FortiOSstated at publication Unknown, now states Known
2 more rows in this change are not listed here. Open all 4 rows
2026-01-14 to2026-08-12Product addedfortianalyzer-bigdatanot named as affected at publication, now names fortianalyzer-bigdata
2026-08-12Product addedCVE-2025-61848fortianalyzer-bigdatanot named as affected at publication, now names fortianalyzer-bigdata
2026-08-12Product addedCVE-2023-42787fortianalyzer-bigdatanot named as affected at publication, now names fortianalyzer-bigdata
1 more row in this change is not listed here. Open all 3 rows
2026-01-27 to2026-08-12Product addedFortianalyzer Cloudnot named as affected at publication, now names fortianalyzer cloud
2026-08-12Product addedCVE-2023-42787Fortianalyzer Cloudnot named as affected at publication, now names fortianalyzer cloud
2026-07-08Product addedCVE-2024-45331Fortianalyzer Cloudnot named as affected at publication, now names fortianalyzer cloud
2 more rows in this change are not listed here. Open all 4 rows
2026-01-14 to2026-08-12Affected range extendedFortianalyzerstated at publication 6.2.12, now states 6.2.13
2026-08-12Affected range extendedCVE-2023-42787Fortianalyzerstated at publication 6.2.12, now states 6.2.13
2026-01-14Affected range extendedCVE-2023-41842Fortianalyzerstated at publication 6.2.12, now states 6.2.13
2026-08-12Affected range extendedCVE-2023-427872 productsstated at publication 6.4.13, now states 6.4.15
2026-08-12Affected range extendedCVE-2023-42787Fortianalyzerstated at publication 6.4.13, now states 6.4.15
2026-08-12Affected range extendedCVE-2023-42787Fortimanagerstated at publication 6.4.13, now states 6.4.15
2026-01-14 to2026-08-12Affected range extendedFortimanagerstated at publication 6.2.12, now states 6.2.13
2026-08-12Affected range extendedCVE-2023-42787Fortimanagerstated at publication 6.2.12, now states 6.2.13
2026-01-14Affected range extendedCVE-2023-41842Fortimanagerstated at publication 6.2.12, now states 6.2.13
2026-07-27Added to CISA KEVCVE-2025-68686FortiOSlisted by CISA 2026-07-27federal fix due 2026-08-10
2026-07-16Added to CISA KEVFortiSandboxlisted by CISA 2026-07-16federal fix due 2026-07-19
2026-07-16Added to CISA KEVCVE-2026-25089FortiSandboxlisted by CISA 2026-07-16federal fix due 2026-07-19
2026-07-16Added to CISA KEVCVE-2026-39808FortiSandboxlisted by CISA 2026-07-16federal fix due 2026-07-19
2026-07-16Affected range extendedCVE-2026-59840Fortiosstated at publication 7.6.2, now states 7.6.3
2026-07-08Affected range extendedCVE-2024-45331Fortianalyzerstated at publication 7.0.13, now states 7.0.16
2026-07-08Affected range extendedFortimanagerstated at publication 7.0.13, now states 7.0.16
2026-07-08Affected range extendedCVE-2024-45331Fortimanagerstated at publication 7.0.13, now states 7.0.16
2026-07-08Affected range extendedCVE-2024-33503Fortimanagerstated at publication 7.0.13, now states 7.0.16
2026-01-14 to2026-07-08Product addedFortimanager Cloudnot named as affected at publication, now names fortimanager cloud
2026-07-08Product addedCVE-2024-33503Fortimanager Cloudnot named as affected at publication, now names fortimanager cloud
2026-07-08Product addedCVE-2024-35276Fortimanager Cloudnot named as affected at publication, now names fortimanager cloud
4 more rows in this change are not listed here. Open all 6 rows
2026-06-09 to2026-07-08Affected range extendedFortiosstated at publication 7.2.12, now states 7.2.13
2026-07-08Affected range extendedCVE-2025-31366Fortiosstated at publication 7.2.12, now states 7.2.13
2026-07-08Affected range extendedCVE-2025-47890Fortiosstated at publication 7.2.12, now states 7.2.13
2 more rows in this change are not listed here. Open all 4 rows
2026-06-09 to2026-07-08Affected range extendedFortiproxystated at publication 7.2.15, now states 7.2.16
2026-07-08Affected range extendedCVE-2025-31366Fortiproxystated at publication 7.2.15, now states 7.2.16
2026-07-08Affected range extendedCVE-2025-47890Fortiproxystated at publication 7.2.15, now states 7.2.16
1 more row in this change is not listed here. Open all 3 rows
2026-06-09 to2026-07-08Affected range extendedFortiosstated at publication 7.0.17, now states 7.0.19
2026-07-08Affected range extendedCVE-2025-31366Fortiosstated at publication 7.0.17, now states 7.0.19
2026-07-08Affected range extendedCVE-2025-47890Fortiosstated at publication 7.0.17, now states 7.0.19
2 more rows in this change are not listed here. Open all 4 rows
2026-02-10 to2026-07-08Affected range extendedFortiproxystated at publication 7.0.21, now states 7.0.23
2026-07-08Affected range extendedCVE-2025-31366Fortiproxystated at publication 7.0.21, now states 7.0.23
2026-07-08Affected range extendedCVE-2025-47890Fortiproxystated at publication 7.0.21, now states 7.0.23
2 more rows in this change are not listed here. Open all 4 rows
2026-07-08Affected range extendedCVE-2025-47890Fortiproxystated at publication 7.4.11, now states 7.4.14
2026-01-14 to2026-07-08Product addedFortisasenot named as affected at publication, now names fortisase
2026-07-08Product addedCVE-2023-42789Fortisasenot named as affected at publication, now names fortisase
2026-06-23Product addedCVE-2025-54821Fortisasenot named as affected at publication, now names fortisase
3 more rows in this change are not listed here. Open all 5 rows
2026-06-09 to2026-06-23Affected range extendedFortiosstated at publication 7.4.9, now states 7.4.11
2026-06-23Affected range extendedCVE-2025-54821Fortiosstated at publication 7.4.9, now states 7.4.11
2026-06-09Affected range extendedCVE-2025-31514Fortiosstated at publication 7.4.9, now states 7.4.11
2026-02-10 to2026-06-23Affected range extendedFortiosstated at publication 7.0.18, now states 7.0.19
2026-06-23Affected range extendedCVE-2025-54821Fortiosstated at publication 7.0.18, now states 7.0.19
2026-02-10Affected range extendedCVE-2025-62631Fortiosstated at publication 7.0.18, now states 7.0.19

A line that names a count is the same change on that many records or products, shown once; it opens to every member. A closed line is not reached by find-in-page; the flat view (Every row, flat →) is. Only counted changes are here: a change a kind's false-positive filter refused, such as a product line being renumbered, is in no figure on this page.

Data sources and quality

One vendor, every counted kind of change: the rows where a CVE record or a CISA KEV entry naming Fortinet changed after publication. The vendor name is the record's own text, compared without regard to case, so one organisation can appear under more than one spelling and this page holds the spellings that share its web address. Rows and records are different numbers and are never added together.

Not counted: a product line being renumbered, a boundary already named in the record's own description, and the other refusal classes are filtered as false positives and are in no figure here, so this page is what survived those filters rather than everything the catalog changed for this vendor.

Not checked: a record published before 2023 cannot have its state at publication recovered and was never compared, and a CISA KEV listing added before the first mirrored commit was never seen changing, so an absence from this page is not evidence that a record held.

How every one of these figures is measured, in full →

Shipped snapshot computed 2026-09-07 from catalog commit f5f9fc6fd7dc. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.