FortiAuthenticator password flaw lets outsiders bypass sign-in
Fortinet fixes a hard-coded password flaw in two FortiAuthenticator branches. Check installed versions and upgrade the affected authentication servers.

FortiAuthenticator handles credential validation for access to protected systems. Fortinet’s November 10 advisory says a hard-coded password flaw in the product can let an unauthenticated attacker bypass credential validation and gain unauthorized access. Two release lines need updates: 8.0.0–8.0.3 and 6.6.0–6.6.10.
Fortinet says the bypass works “in certain circumstances outside of the attacker’s control.” The company rates CVE-2026-126257 critical, with a CVSS v3 score of 9.0, and lists escalation of privilege as the impact. Fortinet does not identify a triggering configuration; prioritize every affected build by installed version.
A password inside credential validation
Fortinet classifies the issue as use of a hard-coded password, CWE-259. Credential validation is supposed to decide whether a presented identity can enter; this flaw gives an unauthenticated outsider a possible route past that decision. Access depends on the circumstances Fortinet describes, which an attacker cannot necessarily reproduce on demand.
Fortinet labels the component “OTHERS.” Inventory installed builds to identify the affected appliances. Fortinet credits Gwendal Guegniaud of its Product Security team with the internal discovery, assisted by the Claude Mythos model.
Fortinet fixes both release lines
| FortiAuthenticator release | Affected installed versions | Upgrade target |
|---|---|---|
8.0 | 8.0.0 through 8.0.3 | 8.0.4 or above |
6.6 | 6.6.0 through 6.6.10 | 6.6.11 or above |
Fortinet marks “Known Exploited” as “No” and “Virtual Patch” as “No” in the advisory. Schedule upgrades based on installed versions and the fixed release for each branch. For an appliance responsible for validating other users’ credentials, unauthorized access has consequences beyond a single login screen.
Inventory the authenticators and upgrade
Locate FortiAuthenticator instances in the identity inventory, including standby or recovery units that could return to service. Read the installed release on each instance and map it to the two affected ranges above. Upgrade an affected 8.0 instance to 8.0.4 or later, and an affected 6.6 instance to 6.6.11 or later, following Fortinet’s upgrade instructions for that instance. Record each instance’s before-and-after build in the change record.
After maintenance, read the running build again on each upgraded instance; the expected result is a release at or above the fixed floor for its branch. Review available authentication and administrator-access records for unexpected access as part of local incident triage. Use the version check to decide exposure: Fortinet supplies no exploit-specific log signature in this advisory. If you find suspicious access, investigate it as a separate incident; an upgrade does not resolve earlier activity.
Give identity and infrastructure teams the installed-build list and an owner for each remaining upgrade.