← Search results
CVE-LINKED INVENTORY124 SECURITY RECORDS
Fortinet, Inc.
FortiOS
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record FortiOS. 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-84392 | 8 Sep 2026 | 7.4.0 ≤ 7.4.12; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16; 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.14; 7.2.0 ≤ 7.2.16; 1.9.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-84393 | 8 Sep 2026 | 7.6.1 ≤ 7.6.6; 7.6.2 ≤ 7.6.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-71407 | 12 Aug 2026 | 7.6.1 ≤ 7.6.6; 1.8.0 ≤ 1.8.4; 1.7.0 ≤ 1.7.2; 1.6.0 ≤ 1.6.2; 1.5.0 ≤ 1.5.1; 1.4.0 ≤ 1.4.3; 1.3.0 ≤ 1.3.1; 1.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-71408 | 12 Aug 2026 | 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.12; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-59840 | 14 Jul 2026 | 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16; 1.7.0; 1.6.0 ≤ 1.6.2; 1.5.0 ≤ 1.5.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-43892 | 14 Jul 2026 | FortiOS: 7.4.0 ≤ 7.4.3, 7.2.0 ≤ 7.2.13, 7.0.0 ≤ 7.0.19 | Upgrade to FortiOS version 7.6.4 or above; Upgrade to FortiOS version 7.4.9 or above; Fortinet remediated this issue in FortiSASE version 25.4.b and hence customers do not need to perform any action.; Upgrade to FortiProxy version 7.6.6 or above; Upgrade to FortiProxy version 7.4.14 or above | Update reference ↗ |
| CVE-2026-23573 | 14 Jul 2026 | 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.12; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16; 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.9; 7.0.0 ≤ 7.0.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-62675 | 14 Jul 2026 | FortiOS: 7.6.0 ≤ 7.6.4, 7.4.0 ≤ 7.4.12, 7.2.0 ≤ 7.2.13, 7.0.0 ≤ 7.0.19, 6.4.0 ≤ 6.4.16; FortiPAM: 1.7.0, 1.6.0 ≤ 1.6.2, 1.5.0 ≤ 1.5.1, 1.4.0 ≤ 1.4.3, 1.3.0 ≤ 1.3.1, 1.2.0, 1.1.0 ≤ 1.1.2, 1.0.0 ≤ 1.0.3; FortiProxy: 7.6.0 ≤ 7.6.4, 7.4.0 ≤ 7.4.14, 7.2.0 ≤ 7.2.16, 7.0.0 ≤ 7.0.23 | Fortinet remediated this issue in FortiSASE version 25.4.b and hence customers do not need to perform any action.; Upgrade to FortiProxy version 7.6.5 or above; Upgrade to FortiOS version 8.0.0 or above; Upgrade to FortiOS version 7.6.5 or above | Update reference ↗ |
| CVE-2025-67862 | 9 Jun 2026 | 7.6.0 ≤ 7.6.1; 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.16; 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.10; 7.2.0 ≤ 7.2.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-53844 | 12 May 2026 | FortiOS: 7.6.0 ≤ 7.6.3, 7.4.0 ≤ 7.4.8, 7.2.0 ≤ 7.2.11, 7.0.0 ≤ 7.0.17, 6.4.0 ≤ 6.4.16, 6.2.0 ≤ 6.2.17, 6.0.0 ≤ 6.0.18 | Upgrade to FortiOS version 7.6.4 or above; Upgrade to FortiOS version 7.4.9 or above; Upgrade to FortiOS version 7.2.12 or above; Upgrade to FortiOS version 7.0.18 or above; Fortinet remediated this issue in FortiSASE version 25.3.a and hence customers do not need to perform any action.; Upgrade to FortiSwitchManager version 7.2.7 or above; Upgrade to FortiSwitchManager version 7.0.6 or above; Fortinet remediated this issue in FortiEdgeCloud version 25.3 and hence customers do not need to perform any action. | Update reference ↗ |
| CVE-2025-61624 | 14 Apr 2026 | 7.6.0 ≤ 7.6.4; 7.4.0 ≤ 7.4.9; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16; 7.4.0 ≤ 7.4.11; 7.2.0 ≤ 7.2.16; 7.0.0 ≤ 7.0.23 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-53847 | 14 Apr 2026 | FortiOS: 7.6.0 ≤ 7.6.3, 7.4.0 ≤ 7.4.8, 7.2.0 ≤ 7.2.11, 7.0.0 ≤ 7.0.17, 6.4.0 ≤ 6.4.16, 6.2.9 ≤ 6.2.17 | Upgrade to FortiOS version 7.6.4 or above; Upgrade to FortiOS version 7.4.9 or above; Upgrade to FortiOS version 7.2.12 or above; Upgrade to FortiOS version 7.0.18 or above | Update reference ↗ |
| CVE-2025-62439 | 10 Feb 2026 | 7.6.0 ≤ 7.6.4; 7.4.0 ≤ 7.4.9; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19 | Update Fortigate NGFW to V7.4.10 or later version with FSSO TS Agent version 5.0 build 0324 or later version. Contact customer support to receive patch and update information | Update reference ↗ |
| CVE-2025-68686 | 10 Feb 2026 | FortiOS: 7.6.0 ≤ 7.6.1, 7.4.0 ≤ 7.4.6, 7.2.0 ≤ 7.2.13, 7.0.0 ≤ 7.0.19, 6.4.0 ≤ 6.4.16 | Upgrade to FortiOS version 7.6.2 or above; Upgrade to FortiOS version 7.4.7 or above | Update reference ↗ |
| CVE-2025-64157 | 10 Feb 2026 | 7.6.0 ≤ 7.6.4; 7.4.0 ≤ 7.4.9; 7.2.0 ≤ 7.2.11; 7.0.0 ≤ 7.0.19 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55018 | 10 Feb 2026 | 7.6.0; 7.4.0 ≤ 7.4.9; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.3 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-22153 | 10 Feb 2026 | 7.6.0 ≤ 7.6.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-25815 | 5 Feb 2026 | ≤ 7.6.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-62631 | 9 Dec 2025 | 7.4.0; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-53843 | 18 Nov 2025 | 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.18; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-58413 | 18 Nov 2025 | 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.18; 6.4.0 ≤ 6.4.16; 6.2.0 ≤ 6.2.17; 6.0.0 ≤ 6.0.18; 25.3.b | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-31514 | 14 Oct 2025 | 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.11; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16; 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.13; 7.2.0 ≤ 7.2.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-25255 | 14 Oct 2025 | 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.11; 7.2.0 ≤ 7.2.15; 7.0.1 ≤ 7.0.22 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-25252 | 14 Oct 2025 | FortiOS: 7.6.0 ≤ 7.6.2, 7.4.0 ≤ 7.4.6, 7.2.0 ≤ 7.2.10, 7.0.0 ≤ 7.0.16, 6.4.0 ≤ 6.4.16 | Upgrade to FortiOS version 7.6.3 or above; Upgrade to FortiOS version 7.4.7 or above | Update reference ↗ |
| CVE-2023-46718 | 14 Oct 2025 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.11; 7.0.0 ≤ 7.0.18; 6.4.6 ≤ 6.4.16; 6.2.9 ≤ 6.2.17; 6.0.13 ≤ 6.0.18; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-47890 | 14 Oct 2025 | 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16; 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.14; 7.2.0 ≤ 7.2.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-58325 | 14 Oct 2025 | 7.6.0; 7.4.0 ≤ 7.4.5; 7.2.5 ≤ 7.2.10; 7.0.0 ≤ 7.0.15; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-58903 | 14 Oct 2025 | 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.18; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-25248 | 12 Aug 2025 | 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.17; 6.4.0 ≤ 6.4.16; 1.5.0; 1.4.0 ≤ 1.4.2; 1.3.0 ≤ 1.3.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-53744 | 12 Aug 2025 | 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.11; 7.0.0 ≤ 7.0.17; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-24477 | 15 Jul 2025 | 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.7; 7.2.4 ≤ 7.2.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-52965 | 8 Jul 2025 | 7.6.0 ≤ 7.6.1; 7.4.0 ≤ 7.4.5; 7.2.0 ≤ 7.2.10; 7.0.1 ≤ 7.0.16; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.20 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-55599 | 8 Jul 2025 | 7.6.0; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.17; 6.4.0 ≤ 6.4.16; 7.6.0 ≤ 7.6.1; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-50568 | 10 Jun 2025 | 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.14; 6.4.2 ≤ 6.4.16; 7.2.0 ≤ 7.2.9; 7.0.0 ≤ 7.0.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-25250 | 10 Jun 2025 | 7.6.0; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19; 6.4.0 ≤ 6.4.16; 25.1.c | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-24471 | 10 Jun 2025 | 7.6.0 ≤ 7.6.1; 7.4.0 ≤ 7.4.7 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-22254 | 10 Jun 2025 | 7.6.0 ≤ 7.6.1; 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15; 7.4.0 ≤ 7.4.7 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-22251 | 10 Jun 2025 | 7.6.0; 7.4.0 ≤ 7.4.5; 7.2.0 ≤ 7.2.11; 7.0.0 ≤ 7.0.17; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-50562 | 10 Jun 2025 | 7.6.0; 7.4.6; 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.17; 6.4.0 ≤ 6.4.16; 1.4.0 ≤ 1.4.1; 1.3.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-47294 | 28 May 2025 | 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.14; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-47295 | 28 May 2025 | 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.14; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-50565 | 8 Apr 2025 | 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.15; 6.4.0 ≤ 6.4.16; 6.2.0 ≤ 6.2.16; 7.0.0 ≤ 7.0.2; 6.4.0 ≤ 6.4.8; 6.0.0 ≤ 6.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-32122 | 8 Apr 2025 | 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.18; 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2019-16151 | 21 Mar 2025 | 6.4.0 ≤ 6.4.1; 6.2.0 ≤ 6.2.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-6697 | 17 Mar 2025 | 6.2.0 ≤ 6.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-29010 | 17 Mar 2025 | 6.2.1 ≤ 6.2.4; 6.0.0 ≤ 6.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-35279 | 11 Feb 2025 | 7.4.0 ≤ 7.4.4; 7.2.4 ≤ 7.2.8 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-40591 | 11 Feb 2025 | 7.6.0; 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.9; 7.0.0 ≤ 7.0.15; 6.4.0 ≤ 6.4.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-36504 | 14 Jan 2025 | 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-46666 | 14 Jan 2025 | 7.6.0; 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
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.