Quick answers
- Is CVE-2026-107656 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107656 being exploited in the wild.
- How severe is CVE-2026-107656?
- Critical severity, with a CVSS score of 9.8, published 26 October 2026.
- Which products and versions are affected?
- Fortinet FortiSandbox 5.0.0 through 5.0.6, 4.4.0 through 4.4.9, 4.2 all versions; Fortinet FortiSandbox PaaS 5.0.0 through 5.0.6, 4.4 all versions, 4.2 all versions.
- Is there a fix for CVE-2026-107656?
- Yes: fixed in FortiSandbox 5.0.7 and above, 4.4.10 and above; FortiSandbox PaaS 5.0.7 and above. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107656 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-107656?
- Check whether you run Fortinet FortiSandbox or Fortinet FortiSandbox PaaS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: FortiSandbox 5.0.7 and above, 4.4.10 and above; FortiSandbox PaaS 5.0.7 and above
Technical details
The vulnerability is an authentication bypass using an alternate path or channel (CWE-288) in the FortiSandbox GUI that allows remote unauthenticated attackers to bypass authentication via crafted HTTP requests. An attacker can exploit this to execute unauthorized code or commands on affected FortiSandbox and FortiSandbox PaaS instances. The vulnerability affects multiple version branches across both the self-hosted and PaaS deployment models.
Affected products
- Fortinet FortiSandbox 5.0.0 through 5.0.6, 4.4.0 through 4.4.9, 4.2 all versions
- Fortinet FortiSandbox PaaS 5.0.0 through 5.0.6, 4.4 all versions, 4.2 all versions
Timeline
- 2026-10-13: disclosed
- 2026-10-26: advisory