Skip to main content
VulnerabilityPublished Updated

CVE-2026-25089: Fortinet FortiSandbox · Execute Unauthorized Code or Commands

Affects Fortinet FortiSandboxSource CVE Database V5

0
Compare

Exploited in the wild · KEV due 19 Jul 2026 · public exploit available · 76% EPSS · patch available : patch Fortinet FortiSandbox now.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS
76.1% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 9 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV 37 days after disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Fortinet, Inc.

    , 131 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 58 minutes after disclosure

  4. , 37 days after disclosure

  5. KEV remediation due

    US federal deadline

    , 40 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Affected software

ProductAffectedFixed in
FortinetFortiSandboxAffected
  • >=5.0.0 <=5.0.5
  • >=4.4.0 <=4.4.8
  • >=4.2.1 <=4.2.8
Fixed in–
FortinetFortiSandbox CloudAffected
  • >=5.0.4 <=5.0.5
Fixed in–
FortinetFortiSandbox PaaSAffected
  • >=5.0.4 <=5.0.5
Fixed in–

CPE configurations (27)

  • cpe:2.3:a:fortinet:fortisandbox:5.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisandbox:5.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisandbox:5.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisandbox:5.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisandbox:5.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisandbox:5.0.0:*:*:*:*:*:*:*

Check the firmware or software version for Fortinet FortiSandbox in the device's admin interface against the vendor advisory.

Description

A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.5, FortiSandbox 4.4.0 through 4.4.8, FortiSandbox 4.2 all versions, FortiSandbox Cloud 5.0.4 through 5.0.5, FortiSandbox PaaS 5.0.4 through 5.0.5 may allow an unauthenticated attacker to execute unauthorized commands via specifically crafted HTTP requests

References

Community reviews

Loading reviews…