Skip to content
Server Security Center
KEVcritical9.1

CVE-2026-25089: Fortinet FortiSandbox OS Command Injection

Fortinet FortiSandbox · listed in the CISA catalog of actively exploited vulnerabilities since 2026-07-16.

CVSS v3.1 (CVE record)
9.1
critical
EPSS (exploit probability, 30 days)
76%
higher than 99.5% of all CVEs
Added to CISA KEV
2026-07-16
US federal due date 2026-07-19
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-25089 explained

CVE-2026-25089 is an OS command injection vulnerability in Fortinet FortiSandbox, FortiSandbox Cloud and FortiSandbox PaaS. An unauthenticated attacker can run unauthorized commands by sending crafted HTTP requests. CISA lists it as known to be exploited, so affected systems need urgent attention.

Impact

A remote attacker with no credentials and no user interaction can execute unauthorized commands on the device over the network. Attack complexity is low. Confidentiality, integrity and availability impact are all high. CISA rates it automatable, meaning it can be exploited at scale without manual steps. CISA also rates the technical impact as total, meaning full control of the affected FortiSandbox. Attackers are known to use this vulnerability. Ransomware use is listed as unknown.

Who is affected

Fortinet FortiSandbox 4.2.1 through 4.2.8, 4.4.0 through 4.4.8 and 5.0.0 through 5.0.5 are affected. The fix is in 4.4.9 and 5.0.6, with 5.2.0 announced as upcoming. The record lists no fixed version within the 4.2 branch. FortiSandbox Cloud 5.0.4 through 5.0.5 is affected and is fixed in 5.0.6 (the record also lists 4.4.9). FortiSandbox PaaS 5.0.4 through 5.0.5 is affected and is fixed in 5.0.6. 5.2.0 is listed as upcoming for both.

Written with AI from the data on this page and checked against it automatically.

Official 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

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Fortinet FortiSandbox
    Affected
    • ≥ 4.2.1, ≤ 4.2.8
    • ≥ 4.4.0, ≤ 4.4.8
    • ≥ 5.0.0, ≤ 5.0.5
    Fixed in
    • 4.4.9
    • 5.0.6
    • 5.2.0 (upcoming)

    Fixed versions taken from the CNA solution text.

  • Fortinet FortiSandbox Cloud
    Affected
    • ≥ 5.0.4, ≤ 5.0.5
    Fixed in
    • 4.4.9
    • 5.0.6
    • 5.2.0 (upcoming)

    Fixed versions taken from the CNA solution text.

  • Fortinet FortiSandbox PaaS
    Affected
    • ≥ 5.0.4, ≤ 5.0.5
    Fixed in
    • 5.0.6
    • 5.2.0 (upcoming)

    Fixed versions taken from the CNA solution text.

How to fix it

  • Update to the fixed version for your product:
    • Fortinet FortiSandbox: 4.4.9, 5.0.6, 5.2.0 (upcoming)
    • Fortinet FortiSandbox Cloud: 4.4.9, 5.0.6, 5.2.0 (upcoming)
    • Fortinet FortiSandbox PaaS: 5.0.6, 5.2.0 (upcoming)
  • Vendor advisory: fortiguard.fortinet.com/psirt/FG-IR-26-141
  • CISA's deadline for US federal agencies: 2026-07-19 (passed) – a useful benchmark for everyone else, too.

Vendor solution:

  • 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.

What to do

  1. Upgrade FortiSandbox to 4.4.9 or 5.0.6 or later, following the Fortinet advisory.
  2. Move FortiSandbox 4.2 systems to a fixed release such as 4.4.9 or 5.0.6. The record lists no fixed 4.2 version.
  3. Confirm that FortiSandbox Cloud and PaaS instances run 5.0.6 or later.
  4. Apply the vendor's mitigations until updates are done. If mitigations are unavailable, follow CISA's guidance or stop using the product.
  5. Restrict network access to FortiSandbox HTTP interfaces and keep them off the internet.
  6. Because exploitation is known, check affected devices for signs of compromise and follow CISA's forensics triage requirements.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-78 Execute unauthorized code or commands

Questions about CVE-2026-25089

Is this vulnerability being exploited?
Yes. CISA added CVE-2026-25089 to its Known Exploited Vulnerabilities catalog on 2026-07-16. The due date for US federal agencies is 2026-07-19. Whether ransomware groups use it is listed as unknown.
Does an attacker need credentials?
No. The attacker needs no authentication and no user interaction. Sending crafted HTTP requests over the network is enough to execute unauthorized commands.
We run FortiSandbox 4.2. What should we do?
The record lists versions 4.2.1 through 4.2.8 as affected. It names no fixed 4.2 version. Plan an upgrade to a fixed release such as 4.4.9 or 5.0.6, as described in the Fortinet advisory.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.