CVE-2026-44277 and CVE-2026-26083: unauthenticated code execution in the Fortinet FortiAuthenticator API and the FortiSandbox web UI
Fortinet fixes unauthenticated code execution in the FortiAuthenticator API and the FortiSandbox web UI
Analysis
CVE-2026-44277 is an improper access control flaw (CWE-284) on FortiAuthenticator's API endpoints that may let an unauthenticated attacker execute unauthorized code or commands through crafted requests; it affects FortiAuthenticator 6.5.0 to 6.5.6, 6.6.0 to 6.6.8, 8.0.0 and 8.0.2, is fixed in 6.5.7, 6.6.9 and 8.0.3, does not affect FortiAuthenticator Cloud, and can be worked around by disabling API access on exposed interfaces under Network, Interfaces, Access Rights (Fortinet FG-IR-26-128). CVE-2026-26083 is a missing authorization flaw (CWE-862) in the web UI of FortiSandbox, FortiSandbox Cloud and FortiSandbox PaaS with the same effect through HTTP requests; FortiSandbox is fixed in 4.4.9 and 5.0.2, FortiSandbox Cloud 5.0 in 5.0.6 and FortiSandbox PaaS 4.4 and 5.0 in 4.4.9 and 5.0.2, while FortiSandbox Cloud 23 and 24 and PaaS 21.3 to 23.4 must migrate to a fixed release (Fortinet FG-IR-26-136). Fortinet discovered both internally, rates each Critical with a CVSSv3 base score of 9.8 and a temporal score of 9.1, and marked neither as known exploited when it published on 2026-05-12 (Fortinet FG-IR-26-128; Fortinet FG-IR-26-136). ENISA's EUVD records carry the 9.1 figure and also list FortiAuthenticator 6.4.0 to 6.4.10 and FortiSandbox 4.2.1 to 4.2.8 as affected (EUVD-2026-29729; EUVD-2026-29550), branches for which Fortinet's advisories, as read on 2026-10-21, name no fixed release (Fortinet FG-IR-26-128; Fortinet FG-IR-26-136).
Cited evidence
in FortiAuthenticator may allow an unauthenticated attacker to execute unauthorized code or commands via crafted requests.
FortiAuthenticator Cloud is not impacted by the issue and hence customers do not need to perform any action.
in FortiSandbox, FortiSandbox Cloud and FortiSandbox PaaS WEB UI may allow an unauthenticated attacker to execute unauthorized code or commands via HTTP requests.
Updates1
Fortinet rates both flaws at a CVSSv3 base score of 9.8 with a temporal score of 9.1 (Fortinet FG-IR-26-128; Fortinet FG-IR-26-136), and 9.1 is the figure ENISA's EUVD records carry (EUVD-2026-29729). The EUVD records also list FortiAuthenticator 6.4.0 to 6.4.10 and FortiSandbox 4.2.1 to 4.2.8 as affected (EUVD-2026-29550), branches for which Fortinet names no fixed release, and FortiSandbox Cloud 23 and 24 and PaaS 21.3 to 23.4 must migrate to a fixed release (Fortinet FG-IR-26-136). The mitigation Fortinet gives until FortiAuthenticator is upgraded is to disable API access on exposed interfaces under Network, Interfaces, Access Rights (Fortinet FG-IR-26-128).
Sources6
Revision history
- Published 2026-05-13-c148b9a5
- Improvement 2026-10-21T1148Z-audit
Fortinet scores CVE-2026-44277 and CVE-2026-26083 at a CVSSv3 base of 9.8 with a temporal score of 9.1, the figure ENISA's EUVD records carry. Those records also list FortiAuthenticator 6.4.0 to 6.4.10 and FortiSandbox 4.2.1 to 4.2.8 as affected, branches Fortinet's advisories give no fix for, and FortiSandbox Cloud 23 and 24 and PaaS 21.3 to 23.4 must migrate to a fixed release; until FortiAuthenticator is upgraded, Fortinet's workaround is to disable API access on exposed interfaces.
Changed: affected_products body classification cves evidence headline sources sourcing_note summary techniques title event_date
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.