FORTIAUTHENTICATOR · CVE-2026-126238 · Vendor
FIX → 8.0.4 · 6.6.11 ✓ verified
Fortinet FG-IR-26-253: an incorrect authorization flaw in the FortiAuthenticator REST API lets an unauthenticated attacker bypass authorization checks and reach restricted functions. CVSS 8.6. Fixed in 8.0.4 and 6.6.11; no workaround. Not known to be exploited.
first public Nov 11, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running self-hosted FortiAuthenticator 8.0.0 to 8.0.3 or 6.6.0 to 6.6.10, an identity and MFA server, whose API is reachable by an attacker. Fortinet says no authentication is needed. Teams that do not run FortiAuthenticator, or already run 8.0.4 / 6.6.11 or later, can skip it.
Not affected if fixed-version, management-interface-not-exposed, versions-outside-affected-ranges
Who cares fortiauthenticator, fortinet, rest-api, self-hosted
get system status)8.0.0 to 8.0.3 or 6.6.0 to 6.6.10A incorrect authorization vulnerability in Fortinet FortiAuthenticator 8.0.0 through 8.0.3, FortiAuthenticator 6.6.0 through 6.6.10 may allow an unauthenticated attacker to bypass authorization checks and gain unauthorized access to restricted functionality.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 8.0.4 · 6.6.11
8.0.4 or above; 6.6.x to 6.6.11 or above