Skip to content
Patcharo

FortiSandbox

Fortinet FortiSandbox 4.2

Vulnerabilities, fixed releases, vendor recommendation and support status of the 4.2 branch, from official sources.

This page is public but not yet offered to search engines: Patcharo cannot state enough sourced facts about this branch.

Sources last modified 23 Jul 2026 · Last verified by Patcharo: 1 Oct 2026 at 09:31 UTC

1
Matched CVEs

including 1 critical

1
CISA KEV
none stated
Newest fix stated
End of life · 14 Nov 2025
Support

In brief

Recommended maintenance build
No official recommendation
Recommended release
No official recommendation
Releases listed by the vendor
No release list read from the vendor
CERT-FR
1 document

Vulnerabilities affecting 4.2

Each record matched to this branch with the fixed release the source states, newest first.

  1. CVE-2026-25089KEV

    Fortinet FortiSandbox OS Command Injection Vulnerability

    Critical9.8CVSS 3.1, Critical
    First fixed releaseNot published in the sources followed
    Published

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.

Support status

From the vendor's published life-cycle policy; support is not a recommendation.

  1. 4.2
    SupportEnd of life
    End of support14 Nov 2025

Fortinet Product Life Cycle (software) · retrieved 1 Oct 2026 at 13:38 UTC

CERT-FR advisories and alerts

Documents of the French national CERT referencing these CVEs, newest first.

  • Advisory (AVI)CERTFR-2026-AVI-0725Multiple vulnerabilities in Fortinet productsPublished 10 Jun 2026

Some titles in this list are machine-translated by artificial intelligence (Mistral AI) from the source texts; each record shows the original.

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.

Read the methodologyRead the guide: FortiOS version numbering: branches, patch releases and the Feature and Mature labels

Other FortiSandbox branches

All FortiSandbox vulnerabilities and branches

Official sources