← Search results
CVE-LINKED INVENTORY64 SECURITY RECORDS
Fortinet, Inc.
FortiWeb
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 FortiWeb. 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-26035 | 12 Aug 2026 | 8.0.0 ≤ 8.0.2; 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.11; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-70466 | 12 Aug 2026 | FortiWeb: 8.0.0 ≤ 8.0.2, 7.6.0 ≤ 7.6.5, 7.4.0 ≤ 7.4.13, 7.2.0 ≤ 7.2.13, 7.0.0 ≤ 7.0.12; FortiOS: 7.6.0 ≤ 7.6.7, 7.4.0 ≤ 7.4.11, 7.2.0 ≤ 7.2.13, 7.0.0 ≤ 7.0.19, 6.4.0 ≤ 6.4.16 | Upgrade to FortiWeb version 8.0.3 or above; Upgrade to FortiWeb version 7.6.6 or above | Update reference ↗ |
| CVE-2026-40688 | 14 Apr 2026 | 8.0.0 ≤ 8.0.3; 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-39811 | 14 Apr 2026 | 8.0.0 ≤ 8.0.3; 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.12; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-39814 | 14 Apr 2026 | 8.0.0 ≤ 8.0.2; 7.6.0 ≤ 7.6.6; 7.4.1 ≤ 7.4.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66178 | 10 Mar 2026 | 8.0.0 ≤ 8.0.1; 7.6.0 ≤ 7.6.5; 7.4.0 ≤ 7.4.11; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24641 | 10 Mar 2026 | 8.0.0 ≤ 8.0.2; 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.12; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24640 | 10 Mar 2026 | 8.0.0 ≤ 8.0.2; 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.12; 7.2.0 ≤ 7.2.12; 7.0.2 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24017 | 10 Mar 2026 | 8.0.0 ≤ 8.0.2; 7.6.0 ≤ 7.6.5; 7.4.0 ≤ 7.4.10; 7.2.0 ≤ 7.2.11; 7.0.0 ≤ 7.0.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-48840 | 10 Mar 2026 | 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-30897 | 10 Mar 2026 | 8.0.0 ≤ 8.0.3; 7.6.0 ≤ 7.6.6; 7.4.0 ≤ 7.4.11; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59719 | 9 Dec 2025 | 8.0.0; 7.6.0 ≤ 7.6.4; 7.4.0 ≤ 7.4.9 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-64471 | 9 Dec 2025 | FortiWeb: 8.0.0 ≤ 8.0.1, 7.6.0 ≤ 7.6.5, 7.4.0 ≤ 7.4.10, 7.2.0 ≤ 7.2.11, 7.0.0 ≤ 7.0.11 | Upgrade to FortiWeb version 8.0.2 or above; Upgrade to FortiWeb version 7.6.6 or above; Upgrade to FortiWeb version 7.4.11 or above; Upgrade to FortiWeb version 7.2.12 or above; Upgrade to FortiWeb version 7.0.12 or above | Update reference ↗ |
| CVE-2025-64447 | 9 Dec 2025 | FortiWeb: 8.0.0 ≤ 8.0.1, 7.6.0 ≤ 7.6.5, 7.4.0 ≤ 7.4.10, 7.2.0 ≤ 7.2.11, 7.0.0 ≤ 7.0.11 | Upgrade to FortiWeb version 8.0.2 or above; Upgrade to FortiWeb version 7.6.6 or above; Upgrade to FortiWeb version 7.4.11 or above; Upgrade to FortiWeb version 7.2.12 or above; Upgrade to FortiWeb version 7.0.12 or above | Update reference ↗ |
| CVE-2025-59669 | 18 Nov 2025 | 7.6.0; 7.4.0 ≤ 7.4.11; 7.2.0 ≤ 7.2.12; 7.0.0 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-58034 | 18 Nov 2025 | FortiWeb: 7.6.0 ≤ 7.6.4, 7.4.0 ≤ 7.4.8, 7.2.0 ≤ 7.2.11, 7.0.2 ≤ 7.0.11 | Upgrade to FortiWeb version 8.0.2 or above; Upgrade to FortiWeb version 7.6.6 or above; Upgrade to FortiWeb version 7.4.11 or above; Upgrade to FortiWeb version 7.2.12 or above; Upgrade to FortiWeb version 7.0.12 or above | Update reference ↗ |
| CVE-2025-64446 | 14 Nov 2025 | FortiWeb: 8.0.0 ≤ 8.0.1, 7.6.0 ≤ 7.6.4, 7.4.0 ≤ 7.4.9, 7.2.0 ≤ 7.2.11, 7.0.0 ≤ 7.0.11 | Upgrade to FortiWeb version 8.0.2 or above; Upgrade to FortiWeb version 7.6.5 or above; Upgrade to FortiWeb version 7.4.10 or above; Upgrade to FortiWeb version 7.2.12 or above; Upgrade to FortiWeb version 7.0.12 or above | Update reference ↗ |
| CVE-2025-53609 | 9 Sep 2025 | 7.6.0 ≤ 7.6.4; 7.4.0 ≤ 7.4.8; 7.2.0 ≤ 7.2.11; 7.0.2 ≤ 7.0.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-47857 | 12 Aug 2025 | 7.6.0 ≤ 7.6.3; 7.4.1 ≤ 7.4.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27759 | 12 Aug 2025 | 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52970 | 12 Aug 2025 | 7.6.0 ≤ 7.6.3; 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-32766 | 12 Aug 2025 | 7.6.0 ≤ 7.6.3; 7.4.1 ≤ 7.4.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-25257 | 17 Jul 2025 | FortiWeb: 7.6.0 ≤ 7.6.3, 7.4.0 ≤ 7.4.7, 7.2.0 ≤ 7.2.10, 7.0.0 ≤ 7.0.10 | Upgrade to FortiWeb version 7.6.4 or above; Upgrade to FortiWeb version 7.4.8 or above; Upgrade to FortiWeb version 7.2.11 or above; Upgrade to FortiWeb version 7.0.11 or above | Update reference ↗ |
| CVE-2024-46671 | 8 Apr 2025 | 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-25254 | 8 Apr 2025 | 7.6.0 ≤ 7.6.2; 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.11; 7.0.0 ≤ 7.0.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-55594 | 14 Mar 2025 | 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-29059 | 14 Mar 2025 | 7.0.0 ≤ 7.0.1; 6.4.0 ≤ 6.4.3; 6.3.0 ≤ 6.3.23; 6.2.3 ≤ 6.2.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-42784 | 11 Mar 2025 | 7.4.0 ≤ 7.4.7; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-55597 | 11 Mar 2025 | 7.6.0; 7.4.0 ≤ 7.4.5; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-50567 | 11 Feb 2025 | 7.6.0; 7.4.0 ≤ 7.4.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-50569 | 11 Feb 2025 | 7.6.0; 7.4.0 ≤ 7.4.5; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-21758 | 14 Jan 2025 | 7.4.0 ≤ 7.4.1; 7.2.0 ≤ 7.2.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-55593 | 14 Jan 2025 | 7.6.0 ≤ 7.6.1; 7.4.0 ≤ 7.4.6; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.3; 6.3.6 ≤ 6.3.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-36509 | 12 Nov 2024 | 7.6.0; 7.4.0 ≤ 7.4.3; 7.2.0 ≤ 7.2.10; 7.0.0 ≤ 7.0.10; 6.3.0 ≤ 6.3.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-33509 | 9 Jul 2024 | 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.3; 6.3.0 ≤ 6.3.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-23665 | 3 Jun 2024 | 7.4.0 ≤ 7.4.2; 7.2.0 ≤ 7.2.7; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.3; 6.3.0 ≤ 6.3.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-23107 | 3 Jun 2024 | 7.4.0; 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.8; 6.3.0 ≤ 6.3.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-46713 | 13 Dec 2023 | 7.4.0; 7.2.0 ≤ 7.2.5; 7.0.0 ≤ 7.0.10; 6.3.0 ≤ 6.3.23; 6.2.0 ≤ 6.2.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-34984 | 13 Sep 2023 | 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.6; 6.4.0 ≤ 6.4.3; 6.3.6 ≤ 6.3.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-23777 | 11 Jul 2023 | 7.0.0 ≤ 7.0.1; 6.4.0 ≤ 6.4.3; 6.3.6 ≤ 6.3.18 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-33305 | 13 Jun 2023 | 7.2.0 ≤ 7.2.1; 7.0.0 ≤ 7.0.6; 6.4.0 ≤ 6.4.3; 6.3.0 ≤ 6.3.23; 7.2.0 ≤ 7.2.4; 7.0.0 ≤ 7.0.10; 6.4.0 ≤ 6.4.13; 6.2.0 ≤ 6.2.15 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-43955 | 11 Apr 2023 | 7.0.0 ≤ 7.0.3; 6.4.0 ≤ 6.4.2; 6.3.0 ≤ 6.3.21; 6.2.0 ≤ 6.2.7; 6.1.0 ≤ 6.1.3; 6.0.0 ≤ 6.0.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-43948 | 11 Apr 2023 | 7.0.0 ≤ 7.0.3; 7.1.0 ≤ 7.1.1; 6.2.0 ≤ 6.2.6; 6.1.0 ≤ 6.1.6; 6.0.0 ≤ 6.0.4; 5.4.0 ≤ 5.4.5; 5.3.0 ≤ 5.3.7; 5.2.0 ≤ 5.2.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-39951 | 7 Mar 2023 | 7.0.0 ≤ 7.0.2; 6.4.0 ≤ 6.4.2; 6.3.6 ≤ 6.3.20 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-22636 | 27 Feb 2023 | 7.0.0 ≤ 7.0.4; 6.4.0 ≤ 6.4.2; 6.3.6 ≤ 6.3.21 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-40683 | 16 Feb 2023 | 7.0.0 ≤ 7.0.3 | 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-2023-23778 | 16 Feb 2023 | 7.0.0 ≤ 7.0.1; 6.4.0 ≤ 6.4.2; 6.3.0 ≤ 6.3.21; 6.2.3 ≤ 6.2.7 | 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-2023-23779 | 16 Feb 2023 | 7.0.0 ≤ 7.0.1; 6.4.0 ≤ 6.4.2; 6.3.6 ≤ 6.3.19 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-30306 | 16 Feb 2023 | 7.0.0 ≤ 7.0.1; 6.4.0 ≤ 6.4.2; 6.3.6 ≤ 6.3.19 | 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-33871 | 16 Feb 2023 | 7.0.0 ≤ 7.0.1; 6.4.0 ≤ 6.4.2; 6.3.6 ≤ 6.3.19 | 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 ↗ |
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.