# CVE-2026-126257: Hardcoded credentials in FortiAuthenticator

> A hard-coded password in FortiAuthenticator may let unauthenticated attackers bypass credential checks and gain unauthorized access.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** Yes
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-3jjw-p738-9hj8

## What is CVE-2026-126257?

CVE-2026-126257 is a critical hardcoded credentials vulnerability in Fortinet FortiAuthenticator, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A use of hard-coded password 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 credential validation in certain circumstances outside of the attacker's control and gain unauthorized access.

Weakness: CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2026-126257?

Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.


## How do I fix CVE-2026-126257?

No fix has been published for CVE-2026-126257 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126257 being exploited?

There is no known exploitation of CVE-2026-126257 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126257 and fix it if it is affected.

What it is: CVE-2026-126257 is a critical hardcoded credentials vulnerability in Fortinet FortiAuthenticator, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126257 in the wild and no public exploit code.
Exposure: Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.

Affected product: Fortinet FortiAuthenticator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126257/ (Markdown: https://insights.sbomify.com/CVE-2026-126257/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126257
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126257
- OSV: https://osv.dev/vulnerability/CVE-2026-126257

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126257/
Summaries are generated and may contain mistakes; the official description above is the record.