# FortiSandbox VNC Server Exposure Allows Unauthenticated Access to Scanning VMs (CVE-2026-59835)

> FortiSandbox 5.0.0-5.0.2 and 4.4.3-4.4.8, including the FSA-500G and FSA-1500G hardware appliances, expose the VNC server bound to malware-scanning virtual machines to unauthenticated network requests. An attacker with network reach to the appliance's scanning subnet can reach and interact with the VNC console of the scanning VMs without any credentials, risking information disclosure and manipulation of the sandbox detonation environment. Fortinet has released fixed builds (5.0.3+, 4.4.9+); no in-the-wild exploitation has been reported as of publication.

- **Published:** 2026-07-14T00:00:00Z
- **Last reviewed:** 2026-07-14T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-1319
- **ID:** TL-2026-1319
- **Severity:** HIGH (CVSS 7.7)
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 · **IOCs:** 22 (full data via the Threadlinqs MCP server — Purple tier)
- **CVEs:** CVE-2026-59835

## Description

CVE-2026-59835 is an Exposure of Resource to Wrong Sphere vulnerability (CWE-668) tracked under Fortinet PSIRT advisory FG-IR-26-145 and published July 14, 2026. FortiSandbox appliances detonate suspicious files inside disposable virtual machines (VMs) that are remotely controlled and inspected via VNC so that analysts and the automated engine can observe malware execution. The affected releases fail to restrict which network segments can reach the VNC listener servicing these scanning VMs: the service is reachable via crafted network requests from unauthenticated sources, rather than being bound to a management-only interface or gated behind the appliance's authentication layer.

An attacker with L3 reachability to a vulnerable FortiSandbox appliance (e.g., inside the perimeter, from an adjacent VLAN, or in cloud deployments with permissive security groups) can connect directly to the VNC port and observe or interact with the scanning VM's framebuffer and input devices. Because the scanning VM is the same environment used to detonate customer-submitted or network-captured files, unauthenticated VNC access carries three concrete risks: (1) information disclosure — an attacker can watch live malware detonation, potentially harvesting proprietary samples, detonation artifacts, or clues about what the organization is investigating; (2) integrity/reliability impact — an attacker with VNC input control could interfere with or corrupt the sandboxing verdicts (e.g., killing analysis processes, injecting inputs that skew behavioral scoring), degrading the security value the appliance is meant to provide; and (3) potential pivot — a scanning VM is designed to safely execute untrusted code, and unauthenticated interactive access to it as an attacker-controlled surface increases the value of any VM-escape research against the underlying hypervisor, though no such escape is described in the source advisory.

FortiSandbox 5.2 and FortiSandbox PaaS (Fortinet-hosted sandbox-as-a-service) are explicitly not affected. The affected on-premises hardware models are the FSA-500G and FSA-1500G appliance SKUs. Fortinet credits its coordinated-disclosure process (INPS security team) and has shipped 5.0.3 and 4.4.9 as remediated builds; the vendor's interim guidance is to restrict network access to the VNC interface until patching is complete.

This disclosure lands amid an active run of FortiSandbox security issues through H1 2026: CVE-2026-25089 (OS command injection via crafted HTTP requests to the web UI, CVSS 9.8, CWE not disclosed in source but consistent with improper input validation on an API endpoint, patched in FortiSandbox 5.0.6/4.4.9), CVE-2026-26083 (Missing Authorization, CWE-862, allowing unauthenticated code/command execution via the web UI across FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS), CVE-2026-39813 (path traversal in the FortiSandbox JRPC API enabling authentication bypass), and CVE-2026-39808 (a further OS command injection vulnerability). Threat-intelligence firm Defused reported active, though described as "vibecoded and likely faulty," exploitation attempts against the CVE-2026-25089/39813/39808 trio in the wild as of mid-June 2026; Fortinet has not confirmed in-the-wild exploitation of any of these at vendor level, and CVE-2026-59835 itself carries no reported exploitation. Defenders operating FortiSandbox should treat the VNC exposure as part of this broader pattern of unauthenticated-access weaknesses on the platform and prioritize patching and network segmentation of the appliance's management and scanning interfaces rather than treating CVE-2026-59835 in isolation.

## MITRE ATT&CK

- T1595 Active Scanning
- T1190 Exploit Public-Facing Application
- T1133 External Remote Services
- T1046 Network Service Discovery
- T1018 Remote System Discovery
- T1219 Remote Access Tools
- T1071 Application Layer Protocol
- T1113 Screen Capture
- T1213 Data from Information Repositories
- T1685 Disable or Modify Tools
- T1070 Indicator Removal
- T1489 Service Stop
- T1583 Acquire Infrastructure
- T1584 Compromise Infrastructure
- T1059 Command and Scripting Interpreter
- T1136 Create Account
- T1505 Server Software Component
- T1105 Ingress Tool Transfer
- T1041 Exfiltration Over C2 Channel
- T1486 Data Encrypted for Impact

## Sources

- [FortiSandbox Vulnerability Allows Unauthenticated Access to VNC Server](https://cybersecuritynews.com/fortisandbox-vulnerability-vnc-server/)
- [FG-IR-26-145 - Unauthenticated VNC Access Exposure](https://fortiguard.fortinet.com/psirt/FG-IR-26-145)
- [Attackers are exploiting FortiSandbox vulnerabilities](https://www.helpnetsecurity.com/2026/06/16/fortisandbox-vulnerabilities-cve-2026-39813-cve-2026-39808-cve-2026-25089/)
- [Fortinet warns of critical RCE flaws in FortiSandbox and FortiAuthenticator](https://www.bleepingcomputer.com/news/security/fortinet-warns-of-critical-rce-flaws-in-fortisandbox-and-fortiauthenticator/)
- [FortiSandbox Triple-CVE: Security Appliances as Network Entry Points](https://labs.cloudsecurityalliance.org/research/csa-research-note-fortisandbox-triple-cve-exploitation-20260/)
- [Fortinet RCE vulnerabilities - Critical flaws in FortiSandbox](https://www.greenbone.net/en/blog/fortinet-rce-vulnerabilities-2026-critical-vulnerabilities-in-fortisandbox/)
- [Three critical FortiSandbox bugs rated 9.8 actively exploited](https://www.scworld.com/news/three-critical-fortisandbox-bugs-rated-98-actively-exploited)
- [CVE-2026-25089: FortiSandbox Command Injection Analysis](https://www.secpod.com/learn/security-research/breaking-down-cve-2026-25089-unauthenticated-command-injection-in-forti-sandbox-forti-sandbox-cloud-and-forti-sandbox-paa-s)
- [Fortinet FortiSandbox: CVE-2026-25089 and CVE-2026-26083 — Critical CVSS 9.8 Vulnerabilities Under Active Exploitation](https://threat-modeling.com/fortinet-fortisandbox-cve-2026-25089-cve-2026-26083-critical-active-exploitation/)
- [FG-IR-26-100 - OS Command Injection through API endpoint](https://www.fortiguard.com/psirt/FG-IR-26-100)

## Full data

Detection queries (Splunk SPL / Microsoft KQL / Sigma) and IOC values require the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-1319