Fortinet FortiSandbox 4.4
Vulnerabilities, fixed releases, vendor recommendation and support status of the 4.4 branch, from official sources.
Patcharo matches 2 vulnerabilities against Fortinet FortiSandbox 4.4: 2 critical, 2 known exploited (CISA KEV). Newest fixed release stated by the vendor on this branch: none stated. Last source modification: 23 Jul 2026.
Last verified by Patcharo: 30 Sept 2026 at 00:17 UTC
In brief
- Matched CVEs
- 2
- CISA KEV
- 2
- Newest fix stated
- none stated
- Support
- No statement in the catalog
- Recommended maintenance build
- No official recommendation
- Recommended release
- No official recommendation
- CERT-FR
- 2 documents
Support status
From the vendor's published life-cycle policy; support is not a recommendation.
The life-cycle policy Patcharo reads states nothing about this branch.
Vendor recommendation
The vendor's own statement about what to run, with its date and source. Separate from vulnerabilities and from support status: being behind a recommendation is not a vulnerability, and a supported release is not necessarily the recommended one.
Fortinet publishes no recommended-release page Patcharo can read. The fixed releases on this site come from the security advisories only; nothing is inferred from version numbers.
Vulnerabilities affecting 4.4
Each record matched to this branch with the fixed release the source states, newest first.
| CVE | Severity | Fixed in | Published |
|---|---|---|---|
| CVE-2026-25089 Fortinet FortiSandbox OS Command Injection Vulnerability | Critical9.8CVSS 3.1, CriticalKEV | after 4.4.8 | |
| CVE-2026-39808 Fortinet FortiSandbox OS Command Injection Vulnerability | Critical9.8CVSS 3.1, CriticalKEV | after 4.4.8 |
CERT-FR advisories and alerts
Documents of the French national CERT referencing these CVEs, newest first.
- Advisory (AVI)CERTFR-2026-AVI-0725Multiples vulnérabilités dans les produits FortinetPublished 10 Jun 2026
- Advisory (AVI)CERTFR-2026-AVI-0440Multiples vulnérabilités dans les produits FortinetPublished 15 Apr 2026
How Patcharo reads this
Affected and fixed releases come from the vendor's structured statements, matched by exact version and patch level. The recommendation is the vendor's own statement; the support status comes from its life-cycle policy. Unknown never becomes Not affected.