Introduction
A hard-coded password in Fortinet FortiAuthenticator can, under conditions Fortinet has not publicly described, let an unauthenticated attacker bypass credential validation on the system many organizations rely on to decide who gets network access. Fortinet rates the issue Critical with a CVSS 3.1 base score of 9.0, and fixed firmware is available for both affected branches, 8.0 and 6.6.
FortiAuthenticator is Fortinet's identity and access management service, intended to prevent unauthorized network access and inappropriate access levels for legitimate users. It provides FortiToken or FIDO2 authentication, LDAP and Active Directory integration, single sign on, and centralized certificate management, and Fortinet reports more than 1 million lifetime customers across its business. Because it sits in the authentication path for other systems, a flaw in its credential validation is a problem for the identity infrastructure as a whole, and its reach extends beyond the appliance itself.
Technical information
Root cause: CWE-259, Use of Hard Coded Password
The assigned weakness is CWE-259. MITRE defines this category as a product containing a password used either for its own inbound authentication or for communication with another component. In this class of flaw, a fixed secret is built into the product and the credential validation logic will accept it.
For FortiAuthenticator specifically, Fortinet states that the vulnerability "may allow an unauthenticated attacker to bypass credential validation in certain circumstances outside of the attacker's control and gain unauthorized access." Fortinet lists the impact as escalation of privilege.
The advisory leaves several things undisclosed, which limits how precisely the issue can be scoped:
- the hard-coded password itself or the account it is tied to
- which component holds the secret (the advisory's component field is simply OTHERS)
- the request format or vulnerable endpoint
- whether the affected path is the management interface, an API, or a particular authentication protocol
- what the "certain circumstances" are
- how 8.0.4 and 6.6.11 change the authentication code
FortiAuthenticator supports many authentication integrations, but that breadth does not tell us which integration, if any, contains the defect. We have treated it as unknown.
The published CVSS vector
NVD displays the following base vector supplied by Fortinet as CNA (NIST has not provided its own assessment):
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- AV:N: network attack vector
- AC:H: high attack complexity, consistent with the vendor's conditional wording. Per the FIRST specification, this metric covers conditions beyond the attacker's control.
- PR:N: no existing privileges required
- UI:N: no user interaction required
- S:C: changed scope
- C:H / I:H / A:H: high potential confidentiality, integrity, and availability impact
The AC:H value is why the score lands at 9.0 rather than 10. Fortinet's advisory also shows a CVSSv3 temporal score of 8.5 with the temporal fields:
E:P/RL:O/RC:C
RL:O (Remediation Level: Official Fix), also recorded by Rapid7, indicates that a vendor-fixed release is available. NVD presents the base vector without these temporal fields.
Attack flow, as far as the public record supports it
Fortinet has not published reproduction details, so the flow below is limited to what the advisory and vector establish:
- The attacker has network reachability to an affected FortiAuthenticator instance (
AV:N) and holds no credentials (PR:N). No victim interaction is needed (UI:N). - Specific circumstances, which the attacker cannot control and which Fortinet has not described, must be present (
AC:H). - When those circumstances hold, the hard-coded password allows credential validation to be bypassed.
- The attacker obtains unauthorized access. Fortinet classifies the impact as escalation of privilege, and the vector records a changed scope with high impact across confidentiality, integrity, and availability.
The public record does not establish a specific privilege level reached, guaranteed appliance takeover, or a code execution chain for this CVE. We recommend describing it as a conditional unauthenticated authentication bypass, not as remote code execution.
Exploitation status
- Fortinet lists "Known Exploited: No", and StackFlag also reports the issue as not known to be exploited. That supports a finding of no confirmed active exploitation in the reviewed reporting. It does not guarantee that exploitation has never occurred.
- The temporal vector's
E:Pvalue is an exploit maturity indicator. It does not name an actor, identify an incident, or point to a public exploit. - No threat actor attribution, indicators of compromise, or CVE-specific detection signatures are disclosed in the advisory or the reviewed StackFlag entry.
- StackFlag labels automated exploitation and full attacker control as "estimated", so neither should be read as an observed outcome.
Patch information
Fortinet fixed CVE-2026-126257 in PSIRT advisory FG-IR-26-271 ("Authentication bypass"), published 10 November 2026. NVD's entry lists this advisory as its only reference. FortiAuthenticator is closed source, so there is no public commit, diff, or code snippet. The fix ships only as new firmware builds.
Fixed releases
- FortiAuthenticator 8.0: vulnerable 8.0.0 through 8.0.3, fixed in 8.0.4 or above
- FortiAuthenticator 6.6: vulnerable 6.6.0 through 6.6.10, fixed in 6.6.11 or above
Each listed branch has its own fix, so 6.6 deployments are not required to migrate to 8.0.
What the fix addresses. In general terms, remediating CWE-259 means removing the built-in secret from the authentication path, or replacing it with a per-device or administrator-set credential, so the shared value is no longer accepted. That describes the weakness class. Fortinet has not confirmed that this is how 8.0.4 and 6.6.11 work. Without a diff, upgrading to a fixed build is the only remediation Fortinet supports.
Deployment notes
- The advisory's Virtual Patch field reads No, so there is no FortiGuard IPS signature to provide interim coverage, and no workaround is documented. Only the firmware update fixes this issue.
- Fortinet's other FortiAuthenticator authentication bypass advisory from the same day, FG-IR-26-265 / CVE-2026-126251 (incorrect authorization, CWE-863, CVSS 9.1), has the same affected ranges and the same fixed builds. Moving to 8.0.4 or 6.6.11 addresses both.
- For these November 2026 advisories, Fortinet recommends reaching the fixed builds via the supported path in its upgrade path tool. The path matters most when jumping several maintenance releases, for example from 6.6.0 to 6.6.11.
- The bug was found internally by Gwendal Guegniaud of Fortinet's Product Security team, using the AI model Claude Mythos, rather than reported externally.
Verifying remediation: On every FortiAuthenticator appliance or VM, confirm the firmware is 8.0.4 or later on the 8.0 branch, or 6.6.11 or later on the 6.6 branch. Any build from 8.0.0 through 8.0.3 or from 6.6.0 through 6.6.10 remains vulnerable.
Affected systems and versions
- Fortinet FortiAuthenticator 8.0.0 through 8.0.3 (fixed in 8.0.4 and above)
- Fortinet FortiAuthenticator 6.6.0 through 6.6.10 (fixed in 6.6.11 and above)
The advisory does not identify a specific vulnerable configuration, and it does not establish the status of release branches it does not list. At the time of writing, the NVD record's vendor field displayed as Unknown. The affected vendor is Fortinet. Fortinet dates initial publication to November 10, 2026, while NVD lists publication on November 11, 2026.
Vendor security history
Fortinet describes a Secure Product Development Lifecycle that includes static and dynamic analysis, fuzzing, and penetration testing, along with a monthly vulnerability advisory schedule. The company states that approximately 60% of its vulnerabilities discovered in 2025 were identified internally, and this CVE is an example of that internal discovery.
That program coexists with a documented history of exploited defects in other products. In its October 30, 2024 alert, CISA added FortiManager CVE-2024-47575 to its Known Exploited Vulnerabilities Catalog based on evidence of active exploitation confirmed by Fortinet, after which Fortinet expanded its guidance with workarounds and indicators of compromise.
FortiAuthenticator itself has had other critical issues this year. The Cyber Security Agency of Singapore's May 15, 2026 alert covered CVE-2026-44277, a separate FortiAuthenticator vulnerability allowing unauthorized code or commands through crafted requests. Neither of these earlier cases is evidence of exploitation of CVE-2026-126257, but both are useful context when prioritizing Fortinet identity infrastructure in patch cycles.
References
- NVD entry for CVE-2026-126257
- CVE.org record for CVE-2026-126257
- Fortinet PSIRT advisory FG-IR-26-271
- Fortinet CSAF advisory for FG-IR-26-271
- Fortinet CVRF advisory for FG-IR-26-271
- Rapid7 Vulnerability Database entry
- Rescana: Fortinet November 2026 PSIRT summary
- AcidPeak threat entry for FG-IR-26-271
- VulDB entry
- StackFlag entry
- Fortinet upgrade path tool
- FortiAuthenticator 8.0.4 upgrade instructions
- FortiAuthenticator 8.0.4 special notices
- FortiAuthenticator 8.0.4 release notes (PDF)
- MITRE CWE-259: Use of Hard Coded Password
- FIRST CVSS v3.1 specification
- Fortinet FortiAuthenticator product page
- Fortinet commitment to product security and integrity (PDF)
- CISA alert on FortiManager CVE-2024-47575 exploitation
- Cyber Security Agency of Singapore alert AL 2026 054
- BleepingComputer coverage of FortiSandbox and FortiAuthenticator flaws
- HKCERT bulletin on Fortinet products



