← 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-2024-54021 | 14 Jan 2025 | 7.6.0; 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.8; 7.4.0 ≤ 7.4.5; 7.2.0 ≤ 7.2.11 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-48886 | 14 Jan 2025 | 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.15; 6.4.0 ≤ 6.4.15; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.17; 2.0.0 ≤ 2.0.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-46668 | 14 Jan 2025 | 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.8; 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-2023-42786 | 14 Jan 2025 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.16; 6.0.0 ≤ 6.0.18 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-42785 | 14 Jan 2025 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.16; 6.0.0 ≤ 6.0.18 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-46670 | 14 Jan 2025 | 7.6.0; 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.9; 7.4.0 ≤ 7.4.5; 7.2.0 ≤ 7.2.11; 7.0.0 ≤ 7.0.18; 2.0.0 ≤ 2.0.14; 1.4.0 ≤ 1.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-46669 | 14 Jan 2025 | 7.4.0 ≤ 7.4.4; 7.2.0 ≤ 7.2.11 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-46665 | 14 Jan 2025 | 7.6.0; 7.4.0 ≤ 7.4.4 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2020-12820 | 19 Dec 2024 | 6.0.0 ≤ 6.0.10; 5.6.0 ≤ 5.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-12819 | 19 Dec 2024 | 6.4.0 ≤ 6.4.1; 6.2.0 ≤ 6.2.4; 6.0.0 ≤ 6.0.10; 5.6.0 ≤ 5.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-33510 | 12 Nov 2024 | 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.16; 7.2.0 ≤ 7.2.9 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-50176 | 12 Nov 2024 | 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.13 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-36505 | 13 Aug 2024 | 7.4.0 ≤ 7.4.3; 7.2.5 ≤ 7.2.7; 7.0.12 ≤ 7.0.14; 6.4.13 ≤ 6.4.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-46720 | 11 Jun 2024 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.12; 6.4.6 ≤ 6.4.15; 6.2.9 ≤ 6.2.16; 6.0.13 ≤ 6.0.18 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-23111 | 11 Jun 2024 | 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.6; 7.0.0 ≤ 7.0.13; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-23110 | 11 Jun 2024 | 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.6; 7.0.0 ≤ 7.0.13; 6.4.0 ≤ 6.4.14; 6.2.0 ≤ 6.2.15; 6.0.0 ≤ 6.0.18 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-46714 | 14 May 2024 | 7.4.0 ≤ 7.4.1; 7.2.1 ≤ 7.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-44247 | 14 May 2024 | 6.4.0 ≤ 6.4.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-26007 | 14 May 2024 | 7.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-48784 | 9 Apr 2024 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.7; 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-2023-41677 | 9 Apr 2024 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.6; 7.0.0 ≤ 7.0.12; 6.4.0 ≤ 6.4.14; 6.2.0 ≤ 6.2.15; 6.0.0 ≤ 6.0.18; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.13 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-23662 | 9 Apr 2024 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.5; 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-2023-46717 | 12 Mar 2024 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.6; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-23112 | 12 Mar 2024 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.6; 7.0.1 ≤ 7.0.13; 6.4.7 ≤ 6.4.14; 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-29180 | 22 Feb 2024 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.11; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.14; 6.0.0 ≤ 6.0.16; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.10; 2.0.0 ≤ 2.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-47537 | 15 Feb 2024 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.6; 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-2024-21762 | 9 Feb 2024 | FortiProxy: 7.4.0 ≤ 7.4.2, 7.2.0 ≤ 7.2.8, 7.0.0 ≤ 7.0.14, 2.0.0 ≤ 2.0.13, 1.2.0 ≤ 1.2.13, 1.1.0 ≤ 1.1.6, 1.0.0 ≤ 1.0.7; FortiOS: 7.4.0 ≤ 7.4.2, 7.2.0 ≤ 7.2.6, 7.0.0 ≤ 7.0.13, 6.4.0 ≤ 6.4.14, 6.2.0 ≤ 6.2.15, 6.0.0 ≤ 6.0.17 | Please upgrade to FortiProxy version 7.4.3 or above; Please upgrade to FortiProxy version 7.2.9 or above; Please upgrade to FortiProxy version 7.0.15 or above; Please upgrade to FortiProxy version 2.0.14 or above; Please upgrade to FortiOS version 7.6.0 or above; Please upgrade to FortiOS version 7.4.3 or above; Please upgrade to FortiOS version 7.2.7 or above; Please upgrade to FortiOS version 7.0.14 or above; Please upgrade to FortiOS version 6.4.15 or above; Please upgrade to FortiOS version 6.2.16 or above | Update reference ↗ |
| CVE-2023-44250 | 10 Jan 2024 | 7.4.0 ≤ 7.4.1; 7.2.5 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-47536 | 13 Dec 2023 | 7.2.0; 7.0.0 ≤ 7.0.13; 6.4.0 ≤ 6.4.14; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 2.0.0 ≤ 2.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-41678 | 13 Dec 2023 | 7.0.0 ≤ 7.0.5; 1.1.0 ≤ 1.1.1; 1.0.0 ≤ 1.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-36639 | 13 Dec 2023 | 7.4.0; 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.11; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.15; 6.0.0 ≤ 6.0.17; 1.1.0; 1.0.0 ≤ 1.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-28002 | 14 Nov 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.12; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.16; 6.0.0 ≤ 6.0.18; 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.19 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-37935 | 10 Oct 2023 | 7.4.0; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-41675 | 10 Oct 2023 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.10; 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.8 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-41841 | 10 Oct 2023 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.11 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-36555 | 10 Oct 2023 | 7.2.0 ≤ 7.2.4 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-33301 | 10 Oct 2023 | 7.4.0; 7.2.0 ≤ 7.2.4 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-29182 | 17 Aug 2023 | 7.0.0 ≤ 7.0.3; 6.4.0 ≤ 6.4.14; 6.2.0 ≤ 6.2.15 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28001 | 11 Jul 2023 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-33307 | 16 Jun 2023 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.10; 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.8 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-33306 | 16 Jun 2023 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.12; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-29175 | 13 Jun 2023 | 7.2.0; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.16; 6.2.0 ≤ 6.2.17; 6.0.0 ≤ 6.0.18; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 2.0.0 ≤ 2.0.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-22639 | 13 Jun 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.15; 6.0.0 ≤ 6.0.17; 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.8; 2.0.0 ≤ 2.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-41327 | 13 Jun 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.8; 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.7 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-22640 | 3 May 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.11; 6.2.0 ≤ 6.2.13; 6.0.0 ≤ 6.0.16; 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.7; 2.0.0 ≤ 2.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-42469 | 11 Apr 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-43947 | 11 Apr 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.13; 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.7; 2.0.0 ≤ 2.0.12; 1.2.0 ≤ 1.2.13 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-22641 | 11 Apr 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.13; 6.0.0 ≤ 6.0.16; 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.8; 2.0.0 ≤ 2.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-42476 | 7 Mar 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.8; 6.4.0 ≤ 6.4.11; 6.2.0 ≤ 6.2.12; 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.7; 2.0.0 ≤ 2.0.11; 1.2.0 ≤ 1.2.13 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-45861 | 7 Mar 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 6.4.0 ≤ 6.4.11; 6.2.0 ≤ 6.2.13; 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.7; 2.0.0 ≤ 2.0.11; 1.2.0 ≤ 1.2.13 | 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.