What is the CVSS score of CVE-2026-25089?

CVE-2026-25089 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 2.0%.

Which versions of Fortinet FortiSandbox are affected by CVE-2026-25089?

Fortinet FortiSandbox (on-premise, Cloud, and PaaS) contains a critical unauthenticated remote code execution vulnerability (CVSS 9.8) allowing attackers to execute arbitrary OS commands via the…

Is there a public PoC exploit available for CVE-2026-25089?

Yes, a public proof-of-concept exploit is available for CVE-2026-25089. Prioritise patching immediately. EPSS: 2.0%.

How to fix or mitigate CVE-2026-25089?

Within 24 hours: Inventory all FortiSandbox instances (on-premise, Cloud, and PaaS); audit network accessibility of management interfaces; enable detailed logging and alerting for suspicious HTTP requests to management endpoints. Within 7 days: Implement network segmentation restricting management interface access to trusted administrator IP ranges only; deploy WAF rules to detect and block exploitation attempts; escalate to Fortinet for patch availability and timeline. Within 30 days: Establish incident response procedures for potential FortiSandbox compromise; evaluate alternative malware analysis solutions if vendor patch timeline extends beyond organizational risk tolerance; document any instances running in internet-facing or cloud-native architectures for priority remediation.

Fortinet FortiSandbox CVE-2026-25089

EUVD-2026-35443 CRITICAL

OS Command Injection (CWE-78)

2026-06-09 fortinet

GHSA-gw24-hwf5-92h2

Fortinet Command Injection Fortisandbox Fortisandbox Cloud Fortisandbox Paas

9.8

CVSS 3.1 · Vendor: fortinet

Severity by source

Vendor (fortinet) PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from Vendor (fortinet) · only source for this CVE.

CVSS VectorVendor: fortinet

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Added to CISA KEV

Jul 16, 2026 - 18:18 CISA

Analysis Updated

Jun 09, 2026 - 16:28 vuln.today

v3 (cvss_changed)

Analysis Updated

Jun 09, 2026 - 16:27 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jun 09, 2026 - 16:22 vuln.today

cvss_changed

CVSS changed

Jun 09, 2026 - 16:22 NVD

9.1 (CRITICAL) 9.8 (CRITICAL)

Analysis Generated

Jun 09, 2026 - 15:46 vuln.today

CVE Published

Jun 09, 2026 - 14:27 nvd

CRITICAL 9.1

DescriptionCVE.org

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

Articles & Coverage 2

POC CVE-2026-25089: Command Injection in Fortinet FortiSandbox VNC/VM API Jun 10, 2026 News Critical OS Command Injection in Fortinet FortiSandbox - CVE-2026-25089 Jun 09, 2026

AnalysisAI

Unauthenticated OS command injection in Fortinet FortiSandbox (on-premise, Cloud, and PaaS variants) allows remote attackers to execute arbitrary operating system commands by sending specifically crafted HTTP requests to the management interface. The flaw carries a CVSS 9.8 rating with network-reachable, no-authentication, no-user-interaction characteristics, and no public exploit identified at time of analysis. Because FortiSandbox is a security-analysis appliance handling untrusted samples, compromise undermines the integrity of malware verdicts and downstream detections.

Technical ContextAI

FortiSandbox is Fortinet's network sandbox appliance for detonating and analyzing suspicious files and URLs, exposing an HTTP-based management and API surface. CWE-78 (Improper Neutralization of Special Elements used in an OS Command) indicates that user-controlled input from HTTP request parameters is incorporated into a shell or system() style invocation without adequate quoting, escaping, or use of safe execve-style APIs, letting metacharacters such as ;, |, $(...) or backticks break out of the intended command. The CPE data confirms three distinct deployment shapes - fortisandbox (appliance/VM), fortisandbox_cloud, and fortisandbox_paas - meaning the vulnerable HTTP handler ships in both customer-managed and Fortinet-hosted forms, so even tenants who never patch their own appliance depend on Fortinet rolling the fix into the managed services.

RemediationAI

Patch available per vendor advisory FG-IR-26-141 (https://fortiguard.fortinet.com/psirt/FG-IR-26-141) - consult that page for the exact fixed builds on the 5.0.x and 4.4.x branches and upgrade FortiSandbox on-premise appliances accordingly; FortiSandbox Cloud and PaaS tenants should confirm with Fortinet that the managed service has been remediated. Customers still on the 4.2 branch (listed as affected in all versions) should plan a migration to a supported branch since a same-branch patch is unlikely. Until upgrade is possible, restrict reachability of the FortiSandbox HTTP management/API interface to a dedicated management network or jump host via firewall ACLs and disable any internet-exposed administrative access; the trade-off is that any integrations (SIEM pulls, FortiGate fabric callbacks, API automation) sourced from outside the management segment will need their source IPs explicitly allow-listed. Monitor HTTP access logs for unusual long query strings, shell metacharacters (;, |, `, $()) in parameters, and unexpected outbound connections from the sandbox host, treating any such activity as potential exploitation.