FortiSandbox 2.1
FORTISANDBOX-2.1Fortinet · OS release · FortiSandbox Series
Unsupported since · 2493 days ago
FortiSandbox 2.1 reached end of support on (2493 days ago).
- Notice published
- 11y 4mo ago
- End of software maintenance
- 8y 4mo ago
- End of security support
- 8y 4mo ago
- End of support
- 6y 10mo ago
Lifecycle Milestones
| Lifecycle notice published | 11y 4mo ago | |
|---|---|---|
| End of software maintenance | 8y 4mo ago | |
| End of security vulnerability support | 8y 4mo ago | |
| Last date of support | 6y 10mo ago |
Known Exploited Vulnerabilities
2 CVEs in CISA's Known Exploited Vulnerabilities catalog are recorded against the Fortinet platform this release belongs to and may apply to this release; verify against the vendor advisory before acting. Fortinet security vulnerability support for this release stopped on . Where one applies, upgrade, isolate, or compensate.
| CVE | KEV added | Vulnerability | Flags |
|---|---|---|---|
CVE-2026-25089
|
Fortinet FortiSandbox OS Command Injection Vulnerability
KEV added 2026-07-16
|
||
CVE-2026-39808
|
Fortinet FortiSandbox OS Command Injection Vulnerability
KEV added 2026-07-16
|
Source: CISA Known Exploited Vulnerabilities catalog. The Ransomware flag reflects CISA's own knownRansomwareCampaignUse field, set when the CVE has been observed in ransomware campaigns per their threat intel. It's not a property of the vulnerability description itself.
Correlation is at the platform level, not per-OS-version (entries disclosed well before this release train shipped are left out). Not exhaustive: KEV only lists actively-exploited CVEs and many relevant unexploited vulnerabilities are not here. Verify against vendor security advisories (PSIRT, JSA, PAN-SA) and NVD before acting. See compensating controls if refresh isn't immediate.
Is FortiSandbox 2.1 still maintained?
No. Fortinet no longer maintains FortiSandbox 2.1; support ended on 2020-01-13. It receives no fixes of any kind, including security patches. Plan an upgrade to a maintained release. See Fortinet's lifecycle bulletin.
When do security fixes for FortiSandbox 2.1 stop?
Fortinet stopped engineering fixes for FortiSandbox 2.1, including security patches, on 2018-07-13. A device on this release cannot be patched against vulnerabilities disclosed after that date without upgrading.
What should I upgrade FortiSandbox 2.1 to?
Upgrade to a currently maintained Fortinet release. Check Fortinet's release notes for the recommended version.
Which known-exploited CVEs may apply to the FortiSandbox 2.1?
2 CVEs in CISA's Known Exploited Vulnerabilities catalog are recorded against Fortinet FortiSandbox and may apply to FortiSandbox 2.1, whose security fixes stopped on 2018-07-13. Verify each against the vendor advisory for the fixed releases before acting. See the Known Exploited Vulnerabilities table for the full list.
FortiSandbox 2.1 Release Lifecycle
FortiSandbox 2.1 is a Fortinet FortiSandbox software release. Releases are maintained on a fixed schedule: Fortinet ships fixes and security patches until the release reaches end of engineering, after which a device must be upgraded to a maintained release to stay patchable. The dates below are milestones for the software train, not for any specific appliance — hardware running this release has its own separate lifecycle. This product has reached end of life as of , meaning Fortinet no longer provides technical support, software updates, or hardware replacement for this product. Organizations still running the FortiSandbox 2.1 should plan a migration .