← Search results
CVE-LINKED INVENTORY44 SECURITY RECORDS
Fortinet
FortiSandbox
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 FortiSandbox. 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-84387 | 8 Sep 2026 | 5.2.0; 5.0.0 ≤ 5.0.6; 4.4.0 ≤ 4.4.9; 4.2.1 ≤ 4.2.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-59835 | 14 Jul 2026 | 5.0.0 ≤ 5.0.2; 4.4.3 ≤ 4.4.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-25089 | 9 Jun 2026 | FortiSandbox: 5.0.0 ≤ 5.0.5, 4.4.0 ≤ 4.4.8, 4.2.1 ≤ 4.2.8; FortiSandbox Cloud: 5.0.4 ≤ 5.0.5; FortiSandbox PaaS: 5.0.4 ≤ 5.0.5 | Upgrade to upcoming FortiSandbox version 5.2.0 or above; Upgrade to FortiSandbox version 5.0.6 or above; Upgrade to FortiSandbox version 4.4.9 or above; Upgrade to upcoming FortiSandbox PaaS version 5.2.0 or above; Upgrade to FortiSandbox PaaS version 5.0.6 or above; Fortinet remediated this issue in FortiSandbox Cloud version 5.2.0 (not released) and hence customers do not need to perform any action.; Fortinet remediated this issue in FortiSandbox Cloud version 5.0.6 (not released) and hence customers do not need to perform any action. | Update reference ↗ |
| CVE-2026-26083 | 12 May 2026 | 5.0.0 ≤ 5.0.1; 4.4.0 ≤ 4.4.8; 4.2.1 ≤ 4.2.8; 23.4.4374; 23.4.4350; 23.3.4329; 23.1.4245; 22.2.4151 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-39813 | 14 Apr 2026 | 5.0.0 ≤ 5.0.5; 4.4.0 ≤ 4.4.8; 24.1; 23.4; 5.0.4 ≤ 5.0.5 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-39812 | 14 Apr 2026 | 5.0.0 ≤ 5.0.4; 4.4.0 ≤ 4.4.8; 4.2.1 ≤ 4.2.8; 5.0.0 ≤ 5.0.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-27316 | 14 Apr 2026 | 5.0.0 ≤ 5.0.5; 4.4.0 ≤ 4.4.9; 23.4.4374; 23.4.4350; 23.3.4329; 23.1.4245; 22.2.4151; 22.2.4134 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-39808 | 14 Apr 2026 | FortiSandbox: 4.4.0 ≤ 4.4.8; FortiSandbox PaaS: 23.4.4374, 23.4.4350, 23.3.4329, 23.1.4245, 22.2.4151, 22.2.4134, 22.1.4113, 21.4.4072, 21.3.4055 | Upgrade to FortiSandbox version 4.4.9 or above; Upgrade to FortiSandbox PaaS version 5.0.2 or above | Update reference ↗ |
| CVE-2025-53608 | 10 Mar 2026 | 5.0.0 ≤ 5.0.2; 4.4.0 ≤ 4.4.7; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52436 | 10 Feb 2026 | 5.0.0 ≤ 5.0.1; 4.4.0 ≤ 4.4.7; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-67685 | 13 Jan 2026 | 5.0.0 ≤ 5.0.4; 4.4.0 ≤ 4.4.8; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53679 | 9 Dec 2025 | 5.0.0 ≤ 5.0.2; 4.4.0 ≤ 4.4.7; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6; 24.1; 23.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-54353 | 9 Dec 2025 | 5.0.0 ≤ 5.0.2; 4.4.0 ≤ 4.4.7; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53949 | 9 Dec 2025 | 5.0.0 ≤ 5.0.2; 4.4.0 ≤ 4.4.7; 4.2.1 ≤ 4.2.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-46215 | 18 Nov 2025 | 5.0.0 ≤ 5.0.1; 4.4.0 ≤ 4.4.7; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-27779 | 18 Jul 2025 | 4.4.0 ≤ 4.4.4; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4; 2.4.0 ≤ 2.4.4; 2.3.0 ≤ 2.3.4; 2.2.0; 2.1.0 ≤ 2.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-26105 | 24 Mar 2025 | 3.2.2; 3.1.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-54027 | 17 Mar 2025 | 5.0.0; 4.4.0 ≤ 4.4.6; 4.2.1 ≤ 4.2.7; 4.0.0 ≤ 4.0.5; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.5 ≤ 3.0.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-54026 | 11 Mar 2025 | 4.4.0 ≤ 4.4.6; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.0 ≤ 3.0.7; 24.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-54018 | 11 Mar 2025 | 4.4.0 ≤ 4.4.4; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-52960 | 11 Mar 2025 | 5.0.0; 4.4.0 ≤ 4.4.6; 4.2.1 ≤ 4.2.7; 4.0.0 ≤ 4.0.6; 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-2024-52961 | 11 Mar 2025 | 5.0.0; 4.4.0 ≤ 4.4.6; 4.2.1 ≤ 4.2.7; 4.0.0 ≤ 4.0.5; 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-2024-45328 | 11 Mar 2025 | 4.4.0 ≤ 4.4.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-27781 | 11 Feb 2025 | 4.4.0 ≤ 4.4.4; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.4; 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-2024-27778 | 14 Jan 2025 | 4.4.0 ≤ 4.4.4; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.4; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.5 ≤ 3.0.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-31490 | 10 Sep 2024 | 4.4.0 ≤ 4.4.4; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.6; 3.2.2 ≤ 3.2.4; 3.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-31491 | 14 May 2024 | 4.4.0 ≤ 4.4.4; 4.2.1 ≤ 4.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-21755 | 9 Apr 2024 | 4.4.0 ≤ 4.4.3; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-21756 | 9 Apr 2024 | 4.4.0 ≤ 4.4.3; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-47540 | 9 Apr 2024 | 4.4.0 ≤ 4.4.2; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4; 3.0.5 ≤ 3.0.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-31487 | 9 Apr 2024 | 4.4.0 ≤ 4.4.4; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.0 ≤ 3.0.7; 2.5.0 ≤ 2.5.2; 2.4.0 ≤ 2.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-23671 | 9 Apr 2024 | 4.4.0 ≤ 4.4.3; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-47541 | 9 Apr 2024 | 4.4.0 ≤ 4.4.2; 4.2.1 ≤ 4.2.6; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.0 ≤ 3.0.7; 2.5.0 ≤ 2.5.2; 2.4.0 ≤ 2.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-41844 | 13 Dec 2023 | 4.4.0 ≤ 4.4.2; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.4 ≤ 3.0.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45587 | 13 Dec 2023 | 4.4.0 ≤ 4.4.2; 4.2.1 ≤ 4.2.8; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-41836 | 13 Oct 2023 | 4.4.0; 4.2.1 ≤ 4.2.4; 4.0.0 ≤ 4.0.6; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.4 ≤ 3.0.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-41843 | 13 Oct 2023 | 4.4.0 ≤ 4.4.1; 4.2.1 ≤ 4.2.5; 4.0.0 ≤ 4.0.3; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.0 ≤ 3.0.7; 2.5.0 ≤ 2.5.2; 2.4.1 | 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-41680 | 13 Oct 2023 | 4.4.0 ≤ 4.4.1; 4.2.1 ≤ 4.2.5; 4.0.0 ≤ 4.0.3; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.0 ≤ 3.0.7; 2.5.0 ≤ 2.5.2; 2.4.1 | 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-41681 | 13 Oct 2023 | 4.4.0 ≤ 4.4.1; 4.2.1 ≤ 4.2.5; 4.0.0 ≤ 4.0.3; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.0 ≤ 3.0.7; 2.5.0 ≤ 2.5.2; 2.4.1 | 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-41682 | 13 Oct 2023 | 4.4.0; 4.2.1 ≤ 4.2.5; 4.0.0 ≤ 4.0.3; 3.2.0 ≤ 3.2.4; 3.1.0 ≤ 3.1.5; 3.0.0 ≤ 3.0.7; 2.5.0 ≤ 2.5.2; 2.4.0 ≤ 2.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-27485 | 11 Apr 2023 | 4.2.0; 4.0.0 ≤ 4.0.2; 3.2.0 ≤ 3.2.3; 3.1.0 ≤ 3.1.5; 3.0.1 ≤ 3.0.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-26115 | 16 Feb 2023 | 4.0.0 ≤ 4.0.2; 3.2.0 ≤ 3.2.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-30305 | 6 Dec 2022 | 4.0.0 ≤ 4.0.2; 3.2.0 ≤ 3.2.3; 3.1.0 ≤ 3.1.5; 4.2.0; 4.1.0 ≤ 4.1.1; 3.3.0 ≤ 3.3.3; 3.2.0 ≤ 3.2.2; 3.1.0 ≤ 3.1.1 | 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-2018-1356 | 9 Apr 2019 | 2.5.2; 2.5.1; 2.5.0; 2.4.1; 2.4.0 | 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.