Introduction
An incorrect authorization flaw in the FortiAuthenticator API may let an unauthenticated attacker with network access bypass authentication and gain unauthorized access to an appliance that many organizations place at the center of their multifactor authentication and single sign-on flows. Fortinet rates CVE-2026-126251 at CVSS 3.1 9.1 (Critical), and the fixed firmware for both affected branches was available roughly three weeks before the advisory was published.
Fortinet's identity and access management product, FortiAuthenticator provides user identification, identity-driven policy, multifactor authentication using FortiToken or FIDO2, single sign-on for internal and cloud resources, and integration with LDAP or Active Directory. Fortinet states it was founded in the San Francisco Bay Area in 2000 and that more than 1,000,000 customers trust its solutions (a vendor statement, not an independent market share measurement). Because FortiAuthenticator sits in the authentication path for other systems, an authorization weakness in it is consequential, although the disclosure does not establish that every connected application or authentication protocol is affected.
The raw CVE data we received lists the vendor as "Unknown." The NVD record and the Fortinet PSIRT advisory (FG-IR-26-265) both identify the affected product as Fortinet FortiAuthenticator.
Technical information
Root cause: CWE-863 in the FortiAuthenticator API
Fortinet classifies the bug as CWE-863, Incorrect Authorization, located in the FortiAuthenticator API, with a stated impact of escalation of privilege. MITRE defines CWE-863 as a product performing an authorization check when an actor attempts to access a resource or perform an action, but performing that check incorrectly. MITRE also distinguishes authorization (AuthZ) from authentication (AuthN).
In this case the underlying weakness is an authorization error, yet Fortinet describes the consequence as an authentication bypass. In practice, a request that should have been rejected was allowed through. Fortinet has not explained the implementation detail that connects the flawed authorization check to the bypass of authentication, and FortiAuthenticator is closed source, so there is no public code to inspect.
CVSS characteristics
NVD displays the following Fortinet (CNA) supplied base vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
- Attack Vector: Network. Exploitation is assessed as possible over the network.
- Attack Complexity: Low. No special conditions are assumed.
- Privileges Required: None. No prior account or role is needed.
- User Interaction: None. No victim action is required.
- Scope: Unchanged. Impact is assessed within the vulnerable component's security scope.
- Confidentiality: None. Integrity: High. Availability: High.
NVD attributes the 9.1 score to Fortinet and showed no independent NIST assessment at the time of the record, so the score should not be presented as a separate NIST validation. The vector also assigns no confidentiality impact. The published impact is authentication bypass and privilege escalation with high integrity and availability impact. The disclosure does not describe it as remote code execution or data theft, and we do not characterize it that way.
Temporal metadata in the CVE record
The CVE record (cvelistV5) also carries an extended vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H/E:F/RL:O/RC:C
Under the FIRST CVSS v3.1 specification:
- E:F (Exploit Code Maturity: Functional) means functional exploit code is available and works in most situations where the vulnerability exists.
- RL:O (Remediation Level: Official Fix) means the vendor has released a complete fix, not just a workaround.
- RC:C (Report Confidence: Confirmed) means the vulnerability report is confirmed.
The E:F value sits alongside Fortinet's separate statement that the issue is not known to be exploited. These fields answer different questions: one is about exploit maturity, the other about observed activity. The E:F metadata does not identify any public repository, exploit author, threat actor, or victim.
Attack flow supported by the disclosure
Based only on what Fortinet and the CVE record publish, the attack shape is:
- The attacker has network reachability to the FortiAuthenticator API (AV:N).
- The attacker holds no credentials and needs no user interaction (PR:N, UI:N).
- The attacker sends API requests that the flawed authorization logic incorrectly permits.
- The result is authentication bypass and unauthorized access, which Fortinet categorizes as escalation of privilege, with high integrity and availability impact in the scoring.
Fortinet has not disclosed the affected endpoint, the HTTP method, the request payload, the exact authorization logic, or the privilege level an attacker ends up with. The sources therefore do not support a reproducible exploitation procedure, nor a claim that exploitation necessarily yields a specific administrator role. Fortinet's hardening blog makes clear this is deliberate, warning that once updates are public, "the fixes themselves reveal where changes were made," and that AI tools can help attackers diff patches and build exploits within hours or days.
Exploitation status
- Fortinet's advisory lists Known Exploited as No.
- The secondary reporting we reviewed (Rescana) makes no exploitation claim, provides no threat actor attribution, and notes that Fortinet published no indicators of compromise for these advisories.
- Rescana reported the CVE absent from the CISA Known Exploited Vulnerabilities catalog at its November 11, 2026 check. That dated observation does not establish later catalog status.
Active exploitation is not publicly confirmed in the reviewed sources, which is different from a guarantee that it has never occurred. The case for prompt remediation rests on the published attack characteristics and impact, not on an attributed campaign.
Patch information
Fortinet fixed CVE-2026-126251 in new FortiAuthenticator firmware for both supported branches. Because the product is closed source, there is no public commit or diff. All evidence comes from Fortinet's advisory, its release notes, and the CVE record.
Fixed versions
- FortiAuthenticator 8.0: vulnerable 8.0.0 through 8.0.3, fixed in 8.0.4 or later.
- FortiAuthenticator 6.6: vulnerable 6.6.0 through 6.6.10, fixed in 6.6.11 or later.
The CNA record gives the same fix in its official solutions entry and sets RL:O (Official Fix), meaning a complete vendor fix rather than a workaround.
How the fix is tracked
The Common Vulnerabilities and Exposures tables in the release notes for both 8.0.4 and 6.6.11 list Bug ID 1334768 and state that the release is "no longer vulnerable" to CVE-2026-126251. Because both branches share the same bug ID, this appears to be one engineering fix backported from 8.0 to 6.6 rather than two independent fixes. In each release it is one of eleven bug IDs (1334764 through 1334803) closing a group of related FortiAuthenticator CVEs, including CVE-2026-126238, CVE-2026-126240 through CVE-2026-126244, and CVE-2026-126248 through CVE-2026-126252. Upgrading therefore closes the whole group, not only this authorization flaw.
What the fix changes, and what we cannot see
Fortinet has not published the vulnerable endpoint, the missing or incorrect check, or any code. All that is known is the bug class: an authorization check that was wrong or incomplete. A fix for this class of bug usually adds or corrects a server-side check of who is making a request and what they are allowed to do, but we could not confirm which component Fortinet changed. The 8.0.4 resolved issues list includes several other access control and authentication fixes in the same release. Fortinet does not link any of them to this CVE, so treat them as background only.
Release timing and build
Fortinet's hardening blog marked FortiAuthenticator 8.0.4 and 6.6.11 as available "Today" when it was published on October 21, 2026. The PSIRT advisory followed on November 10, 2026 as part of Fortinet's monthly release cycle (NVD lists publication on November 11, 2026, a separate publication event). That gave customers about three weeks to upgrade before disclosure.
The 8.0.4 release notes also list regressions introduced during 8.0.4 development that affected only systems which had already installed 8.0.4 build 0187. The release described by the notes resolves them. A prerelease build labeled 8.0.4 is not necessarily the final GA build, so check the exact build number, not just the version string.
Upgrade preparation
- Save a configuration copy before upgrading using Restore/Backup and Download Backup File. The upgrade instructions also recommend a full backup.
- Compute the firmware image's MD5 checksum and compare it with the value Fortinet provides.
- For the 8.0.4 destination, direct upgrades are supported from 6.0.7 or 6.2.1 or later. Systems on 6.0.5 or older must first move to 6.0.7, and systems on 6.1.0 through 6.2.0 must first move to 6.3.3. These paths apply to 8.0.4 specifically.
No virtual patch
The advisory lists Virtual Patch as No. There is no FortiGuard IPS signature that blocks this bug at the network level, and no workaround is published. Fortinet's broader hardening guidance on administrative interface restrictions does not name this CVE and should not be treated as a validated workaround. Installing 8.0.4 or later, or 6.6.11 or later, is the only vendor fix.
Affected systems and versions
- Fortinet FortiAuthenticator 8.0.0 through 8.0.3 (fixed in 8.0.4 or later)
- Fortinet FortiAuthenticator 6.6.0 through 6.6.10 (fixed in 6.6.11 or later)
The affected component is the FortiAuthenticator API, and the attack is classified as unauthenticated. The advisory does not provide a complete affected or unaffected determination for other historical branches, and it does not identify any specific configuration that is required for exposure.
Vendor security history
Fortinet credits discovery of CVE-2026-126251 to Gwendal Guegniaud of its Product Security team, making this an internally found issue. Its security hardening article, published October 21, 2026 and updated November 10, describes incorporating frontier AI models into security testing to analyze code paths, protocol handling, and configuration logic. The article states that the resulting hardening releases include fixes found through that program, and it urges prompt upgrading, particularly for internet-facing devices. That is evidence of an active internal discovery and remediation process, not evidence that unpatched deployments are safe.
Fortinet products have also seen serious exploitation in the past. In April 2025, CISA reported that a threat actor had created a malicious file through previously exploited FortiGate vulnerabilities, including CVE-2024-21762, CVE-2023-27997, and CVE-2022-42475, which could permit read-only access to device files, potentially including configurations. CISA relayed Fortinet's guidance to upgrade, review configurations, and reset potentially exposed credentials. That incident involves FortiGate and different CVEs, so it neither indicates exploitation of this FortiAuthenticator flaw nor means its recovery steps automatically apply here.
References
- NVD entry for CVE-2026-126251
- Official CVE record for CVE-2026-126251 (CVE Services API)
- Fortinet PSIRT advisory FG-IR-26-265 (fortiguard.fortinet.com)
- Fortinet PSIRT advisory FG-IR-26-265 (fortiguard.com)
- FortiAuthenticator 8.0.4 release notes: resolved issues
- FortiAuthenticator 6.6.11 release notes
- FortiAuthenticator 8.0.4 upgrade instructions
- FortiAuthenticator 8.0.4 release notes (PDF)
- CIRCL vulnerability entry for CVE-2026-126251
- Fortinet: Security Hardening Release for Multiple Products
- FortiAuthenticator product page
- About Fortinet
- Fortinet Security Vulnerability Policy
- MITRE CWE-863: Incorrect Authorization
- FIRST CVSS v3.1 Specification
- Rescana: Fortinet November 2026 PSIRT summary
- StackFlag entry for CVE-2026-126251
- VulDB entry for CVE-2026-126251
- CISA: Fortinet advisory on post exploitation technique for known vulnerabilities (April 2025)
- CISA Known Exploited Vulnerabilities feed



