← Search results
CVE-LINKED INVENTORY32 SECURITY RECORDS
Fortinet
FortiProxy
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 Fortinet FortiProxy. 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-59839 | 14 Jul 2026 | 7.6.0 ≤ 7.6.5; 7.4.0 ≤ 7.4.13; 7.2.0 ≤ 7.2.16; 7.0.0 ≤ 7.0.23; 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.9; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.19 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-54822 | 14 Oct 2025 | 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.15; 7.0.0 ≤ 7.0.22; 2.0.0 ≤ 2.0.14; 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.11 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-26008 | 14 Oct 2025 | 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.9; 7.0.0 ≤ 7.0.22; 2.0.0 ≤ 2.0.14; 1.2.0 ≤ 1.2.13; 1.2.0; 1.1.0 ≤ 1.1.2; 1.0.0 ≤ 1.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-25253 | 14 Oct 2025 | 7.6.0 ≤ 7.6.1; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.15; 7.0.0 ≤ 7.0.22; 7.6.0 ≤ 7.6.2; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.18; 1.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-22862 | 2 Oct 2025 | 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.15; 7.0.5 ≤ 7.0.22; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.11; 7.0.6 ≤ 7.0.18 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-26009 | 12 Aug 2025 | 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.15; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.16; 6.0.0 ≤ 6.0.18; 1.2.0; 1.1.0 ≤ 1.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-45584 | 12 Aug 2025 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.13; 7.4.0; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.12; 6.4.0 ≤ 6.4.16; 1.1.0 ≤ 1.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-29184 | 10 Jun 2025 | 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.8; 2.0.0 ≤ 2.0.14; 1.2.0 ≤ 1.2.13; 1.1.0 ≤ 1.1.6; 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-22252 | 28 May 2025 | 7.6.0 ≤ 7.6.1; 7.2.5; 7.6.0; 7.4.4 ≤ 7.4.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-26013 | 8 Apr 2025 | 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.9; 7.0.0 ≤ 7.0.15; 2.0.0 ≤ 2.0.14; 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.11; 6.4.0 ≤ 6.4.14; 6.2.0 ≤ 6.2.13 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-37930 | 8 Apr 2025 | 7.2.0 ≤ 7.2.6; 7.0.0 ≤ 7.0.12; 7.4.0; 7.2.0 ≤ 7.2.5; 7.0.1 ≤ 7.0.11; 6.4.7 ≤ 6.4.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2019-15706 | 17 Mar 2025 | 2.0.0; 1.2.0 ≤ 1.2.9; 6.2.0 ≤ 6.2.1; 6.0.0 ≤ 6.0.8; 5.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-26006 | 14 Mar 2025 | 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.9; 7.0.0 ≤ 7.0.16; 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. | Update reference ↗ |
| CVE-2023-46715 | 14 Jan 2025 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.6; 7.0.0 ≤ 7.0.12; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.16; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-52963 | 14 Jan 2025 | 7.4.0 ≤ 7.4.5; 7.2.0 ≤ 7.2.13; 7.0.0 ≤ 7.0.20; 2.0.0 ≤ 2.0.14; 7.6.0; 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-26015 | 9 Jul 2024 | 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.18; 7.2.0 ≤ 7.2.8; 7.0.0 ≤ 7.0.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-21754 | 11 Jun 2024 | 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.17; 2.0.0 ≤ 2.0.14; 7.4.0 ≤ 7.4.3; 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-45586 | 14 May 2024 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.13; 2.0.0 ≤ 2.0.14; 7.0.0 ≤ 7.0.12; 6.4.0 ≤ 6.4.15; 6.2.0 ≤ 6.2.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-42789 | 12 Mar 2024 | 7.4.0; 7.2.0 ≤ 7.2.6; 7.0.0 ≤ 7.0.12; 2.0.0 ≤ 2.0.13; 23.2.b; 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.5; 6.4.0 ≤ 6.4.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-42790 | 12 Mar 2024 | 7.4.0; 7.2.0 ≤ 7.2.6; 7.0.0 ≤ 7.0.12; 2.0.0 ≤ 2.0.13; 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.5; 6.4.0 ≤ 6.4.14; 6.2.0 ≤ 6.2.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-29179 | 22 Feb 2024 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.10; 7.0.0 ≤ 7.0.11; 6.4.0 ≤ 6.4.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-36641 | 14 Nov 2023 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.10; 2.0.0 ≤ 2.0.13; 1.2.0 ≤ 1.2.13; 1.1.0 ≤ 1.1.6; 1.0.0 ≤ 1.0.7; 7.4.0; 7.2.0 ≤ 7.2.5 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-29183 | 13 Sep 2023 | 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.10; 7.0.0 ≤ 7.0.11; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.14 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-33308 | 26 Jul 2023 | 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.9; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-29178 | 13 Jun 2023 | 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 2.0.0 ≤ 2.0.12; 1.2.0 ≤ 1.2.13; 1.1.0 ≤ 1.1.6; 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.11; 6.4.0 ≤ 6.4.13 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-26207 | 13 Jun 2023 | 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.10; 7.2.0 ≤ 7.2.5 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-43953 | 13 Jun 2023 | 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.7; 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.11; 6.4.0 ≤ 6.4.12; 6.2.0 ≤ 6.2.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-41330 | 11 Apr 2023 | 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.7; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 6.4.0 ≤ 6.4.11; 6.2.0 ≤ 6.2.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-41329 | 7 Mar 2023 | 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.8; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.9; 6.4.0 ≤ 6.4.12; 6.2.3 ≤ 6.2.13 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-42472 | 16 Feb 2023 | 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.7; 2.0.0 ≤ 2.0.10; 1.2.0 ≤ 1.2.13; 1.1.0 ≤ 1.1.6; 7.2.0 ≤ 7.2.2; 7.0.0 ≤ 7.0.8; 6.4.0 ≤ 6.4.11 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-39948 | 16 Feb 2023 | 7.0.0 ≤ 7.0.6; 2.0.0 ≤ 2.0.11; 1.2.0 ≤ 1.2.13; 7.2.0 ≤ 7.2.3; 7.0.0 ≤ 7.0.7; 6.4.0 ≤ 6.4.11; 6.2.0 ≤ 6.2.12; 6.0.0 ≤ 6.0.16 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-40680 | 6 Dec 2022 | 7.0.0 ≤ 7.0.1; 2.0.0 ≤ 2.0.11; 1.2.0 ≤ 1.2.13; 1.1.0 ≤ 1.1.6; 7.0.0 ≤ 7.0.3; 6.4.0 ≤ 6.4.9; 6.2.2 ≤ 6.2.12; 6.0.7 ≤ 6.0.15 | 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.