Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY37 SECURITY RECORDS

Fortinet

FortiAnalyzer

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record Fortinet FortiAnalyzer. Use that record for publisher support phases and retirement dates.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-84391 8 Sep 2026 7.6.3 ≤ 7.6.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-67604 12 May 2026 7.6.0 ≤ 7.6.4; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22629 10 Mar 2026 7.6.0 ≤ 7.6.4; 7.4.0 ≤ 7.4.10; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15; 7.6.2 ≤ 7.6.3; 7.4.1 ≤ 7.4.7; 7.2.1 ≤ 7.2.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-68482 10 Mar 2026 7.6.0 ≤ 7.6.4; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15; 7.6.2 ≤ 7.6.3; 7.4.1 ≤ 7.4.7; 7.2.1 ≤ 7.2.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48418 10 Mar 2026 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.14; 6.4.0 ≤ 6.4.15; 7.6.2; 7.4.1 ≤ 7.4.7; 7.2.1 ≤ 7.2.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-40593 11 Dec 2025 FortiAnalyzer: 7.4.0 ≤ 7.4.2, 7.2.0 ≤ 7.2.5, 7.0.0 ≤ 7.0.15, 6.4.0 ≤ 6.4.15; FortiPortal: 6.0.0 ≤ 6.0.15; FortiOS: 7.6.0, 7.4.4, 7.2.7, 7.0.14; FortiManager: 7.4.0 ≤ 7.4.2, 7.2.0 ≤ 7.2.5, 7.0.0 ≤ 7.0.15, 6.4.0 ≤ 6.4.15 Upgrade to FortiAnalyzer version 7.6.0 or above; Upgrade to FortiAnalyzer version 7.4.3 or above; Upgrade to FortiAnalyzer version 7.2.6 or above; Upgrade to FortiPortal version 7.0.0 or above; Upgrade to FortiOS version 7.6.1 or above; Upgrade to FortiOS version 7.4.5 or above; Upgrade to FortiOS version 7.2.8 or above; Upgrade to FortiOS version 7.0.15 or above; Upgrade to FortiManager version 7.4.3 or above; Upgrade to FortiManager version 7.2.6 or above Update reference ↗
CVE-2025-53845 14 Oct 2025 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.11; 7.0.0 ≤ 7.0.15; 6.4.0 ≤ 6.4.15 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54973 14 Oct 2025 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.10; 7.0.9 ≤ 7.0.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-52962 8 Apr 2025 7.6.0 ≤ 7.6.1; 7.4.0 ≤ 7.4.5; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-40585 14 Mar 2025 7.4.0; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.8; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-40584 11 Feb 2025 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.13; 6.4.0 ≤ 6.4.15; 6.2.2 ≤ 6.2.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-52966 11 Feb 2025 7.6.0; 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.13; 6.4.0 ≤ 6.4.15 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50563 16 Jan 2025 7.6.0 ≤ 7.6.1; 7.4.1 ≤ 7.4.3 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-35273 14 Jan 2025 7.4.0 ≤ 7.4.3; 7.4.0 ≤ 7.4.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-35276 14 Jan 2025 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.12; 6.4.0 ≤ 6.4.14; 7.4.1 ≤ 7.4.3; 7.2.1 ≤ 7.2.5; 7.0.1 ≤ 7.0.11; 6.4.1 ≤ 6.4.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-33505 12 Nov 2024 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.13; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.13; 6.0.0 ≤ 6.0.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-35274 12 Nov 2024 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.13; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32118 12 Nov 2024 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.13; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32116 12 Nov 2024 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.13; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-45330 8 Oct 2024 7.4.0 ≤ 7.4.3; 7.2.2 ≤ 7.2.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-44254 10 Sep 2024 7.4.0; 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.12; 6.4.0 ≤ 6.4.14; 6.2.0 ≤ 6.2.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-40719 14 Nov 2023 7.4.0; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-44256 20 Oct 2023 7.4.0; 7.2.0 ≤ 7.2.3; 7.0.2 ≤ 7.0.8; 6.4.8 ≤ 6.4.13; 7.0.0 ≤ 7.0.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-25607 10 Oct 2023 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.7; 6.4.0 ≤ 6.4.11; 6.2.0 ≤ 6.2.12; 6.0.0 ≤ 6.0.12; 7.1.0; 7.0.0 ≤ 7.0.3; 6.2.0 ≤ 6.2.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-42782 10 Oct 2023 7.4.0; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 6.4.0 ≤ 6.4.13; 6.2.0 ≤ 6.2.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-41838 10 Oct 2023 7.4.0; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.8; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-42788 10 Oct 2023 7.4.0; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.8; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-42787 10 Oct 2023 7.4.0; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.13; 7.2.0 ≤ 7.2.5; 7.0.1 ≤ 7.0.6; 6.4.5 ≤ 6.4.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-22305 1 Sep 2023 7.0.0 ≤ 7.0.2; 6.4.0 ≤ 6.4.7; 6.2.0 ≤ 6.2.11; 6.0.0 ≤ 6.0.12; 4.0.0 ≤ 4.0.2; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.0 ≤ 3.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-43072 18 Jul 2023 7.0.0 ≤ 7.0.2; 6.4.0 ≤ 6.4.7; 6.2.0 ≤ 6.2.12; 6.0.0 ≤ 6.0.12; 5.6.0 ≤ 5.6.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-25609 13 Jun 2023 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.6; 6.4.8 ≤ 6.4.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-22642 11 Apr 2023 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.5; 6.4.8 ≤ 6.4.10; 6.4.0 < 6.4.* No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-42477 11 Apr 2023 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.6; 6.4.0 ≤ 6.4.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-23776 7 Mar 2023 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.4; 6.4.0 ≤ 6.4.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-25611 7 Mar 2023 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.5; 6.4.0 ≤ 6.4.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-30304 16 Feb 2023 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.4; 6.4.0 ≤ 6.4.8; 6.2.0 ≤ 6.2.9; 6.0.0 ≤ 6.0.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-13375 28 May 2019 FortiAnalyzer 5.6.0 and below; FortiManager 5.6.0 and below No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.