Fortinet’s security sandbox appliances are facing active exploitation of three critical vulnerabilities, just days after the vendor issued patches. The flaws, all rated 9.1 on the CVSS scale, allow unauthenticated attackers to bypass authentication, escalate privileges, and execute arbitrary code remotely. While Fortinet released fixes for two of the vulnerabilities in April and the third last week, threat intelligence firm Defused confirmed exploitation began over the weekend, raising concerns about the speed of attacker adoption.
What was patched
The three vulnerabilities affect different components of Fortinet’s sandboxing solutions. CVE-2026-39813, a path traversal bug in the FortiSandbox JRPC API, enables authentication bypass via crafted HTTP requests. It impacts FortiSandbox versions 4.4.0 through 4.4.8 and 5.0.0 through 5.0.5, with fixes available in versions 4.4.9 and 5.0.6. Fortinet credited security analyst Loic Pantano for discovering this flaw.
CVE-2026-39808 and CVE-2026-25089 are both OS command injection vulnerabilities. The former affects FortiSandbox versions 4.4.0 through 4.4.8 and was patched in version 4.4.9. KPMG Spain researcher Samuel de Lucas Maroto reported this bug. The latter, CVE-2026-25089, extends to FortiSandbox Cloud and FortiSandbox PaaS WEB UI, affecting versions 4.4.0 through 4.4.8, 5.0.0 through 5.0.5, and cloud variants 5.0.4 through 5.0.5. Defused noted that no public exploit exists for this flaw, suggesting attackers may be using an unrefined or privately developed exploit.
- Three critical Fortinet sandbox vulnerabilities (CVSS 9.1) under active exploitation
- CVE-2026-39813: Authentication bypass via path traversal in JRPC API
- CVE-2026-39808: OS command injection in FortiSandbox
- CVE-2026-25089: OS command injection in FortiSandbox, Cloud, and PaaS WEB UI
- Exploitation detected within days of patches for CVE-2026-25089
Why exploitation is accelerating
The rapid exploitation of these vulnerabilities aligns with a broader trend of attackers targeting Fortinet products. Earlier this month, Check Point Research warned that ransomware groups had exploited a critical authentication bypass in Fortinet’s Remote Access VPN and Mobile Access deployments. The same groups were suspected of leveraging other VPN-related vulnerabilities in Fortinet’s portfolio. The pattern suggests that threat actors are prioritizing Fortinet appliances due to their widespread use in enterprise and cloud environments, where they often serve as gatekeepers for network security.
Defused’s observation that the exploit for CVE-2026-25089 appears to be "vibe coded"—potentially unstable or hastily developed—indicates that attackers are moving quickly to capitalize on the window between patch release and widespread adoption. This urgency underscores the importance of timely updates, particularly for security appliances that are directly exposed to the internet.
What administrators should do
Fortinet has not responded to inquiries about whether it has observed attacks targeting these vulnerabilities. However, the active exploitation reported by Defused leaves little room for delay. Administrators should prioritize upgrading affected FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS deployments to the patched versions immediately. For environments where immediate patching is not feasible, temporary mitigations—such as restricting access to the sandbox interfaces or implementing additional network-level controls—should be considered.
- Verify all FortiSandbox deployments are running patched versions (4.4.9+, 5.0.6+, or cloud equivalents)
- Isolate sandbox interfaces from public internet access where possible
- Monitor for unusual HTTP request patterns targeting the JRPC API or WEB UI
The speed of exploitation highlights the need for proactive vulnerability management, particularly for security appliances that are frequent targets of opportunistic attacks. Organizations relying on Fortinet’s sandboxing solutions should treat these vulnerabilities as a critical priority to prevent potential breaches or lateral movement within their networks.
Automated pipeline · Security
Synthesized from 1 industry feed on 17 Jun 2026. Passed independent editor verification (score 92/100) before publication. Style guide v1.3.
Sources
Decision trail
- Checking for duplicates — New story No previously published article covers the three critical Fortinet sandbox bugs.
- Writing the article — Draft created article_id=84 slug=fortinet-sandbox-flaws-under-active-attack-after-patches
-
Editor review — Approved
- Score: 92/100
- Factual grounding: The draft states 'Fortinet released fixes for two of the vulnerabilities in April and the third last week.' The source specifies CVE-2026-39813 and CVE-2026-39808 were patched in April, but does not provide an exact date for CVE-2026-25089 beyond 'last week.' The phrasing is technically correct but could be more precise by avoiding the implication of a specific timeline for the third patch.
- No copied phrasing: The draft closely mirrors the source's phrasing in describing the vulnerabilities (e.g., 'path traversal bug in the FortiSandbox JRPC API' and 'OS command injection vulnerabilities'). While the facts are correct, the structure and wording are too similar to the source. Restructuring would improve originality.
- Style compliance: The body length (approximately 600 words) is within the 300-700 word range, but the draft leans toward the upper limit for a story with sparse additional context. The article could be tightened slightly without losing substance.
- Quote integrity: The draft does not use any blockquotes, so this check is not applicable. However, the source includes a direct quote from Defused ('vibe coded'), which could have been used verbatim if formatted as a blockquote. This is not a violation but a missed opportunity for compliance with the style guide.
- Generating reader Q&A — Generated 4 items
- Assigning hero image — Pexels pexels_id=4597280
- Linking related stories — Linked 3 relations from 60 candidates
- Publishing — Published fortinet-sandbox-flaws-under-active-attack-after-patches

Discussion · coming soon
Be the first to join the thread when community discussion launches.