FORTIAUTHENTICATOR · CVE-2026-126242 · Vendor
FIX → 8.0.4 · 6.6.11 ✓ verified
FortiAuthenticator 8.0.0 through 8.0.3 and 6.6.0 through 6.6.10 have an incorrect authorization flaw. An attacker can bypass authentication and gain unauthorized access, though full impersonation also requires identifiers and data obtained another way.
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.
Teams running self-hosted FortiAuthenticator 8.0.0-8.0.3 or 6.6.0-6.6.10. Fortinet describes an unauthenticated incorrect-authorization flaw in the API that can bypass authentication; full impersonation needs the attacker to already hold pre-required IDs and data obtained another way (hence the high attack complexity, CVSS 7.4). Fortinet does not name a required setting, so any instance on an affected version should be upgraded; instances on 8.0.4+/6.6.11+ can skip it.
Not affected if unknown
Who cares fortiauthenticator, fortinet, self-hosted, unauthenticated
get system status on the CLI)8.0.0 through and through A incorrect authorization vulnerability in Fortinet FortiAuthenticator 8.0.0 through 8.0.3, FortiAuthenticator 6.6.0 through 6.6.10 may allow an attacker to bypass authentication and gain unauthorized access. Full impersonation however requires the attacker to obtain pre-required id and data via other means.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
8.0.36.6.06.6.10Upgrade to 8.0.4 · 6.6.11
8.0.4 or above; 6.6.x to 6.6.11 or above