FORTIAUTHENTICATOR · CVE-2026-126247 · Infrastructure
FIX → 8.0.4 · 6.6.11 ✓ verified
A format string flaw in Fortinet FortiAuthenticator 8.0.0 through 8.0.3 and 6.6.0 through 6.6.10 can be triggered through crafted HTTP requests. An authenticated privileged attacker may be able to execute unauthorized code or commands on the appliance.
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.
Self-hosted FortiAuthenticator appliances on 8.0.0-8.0.3 or 6.6.0-6.6.10. The flaw is in the API/HTTP handling and needs an authenticated privileged account, so the risk is mainly a compromised or malicious admin. Teams without FortiAuthenticator, or on 8.0.4 / 6.6.11 or later, can skip it.
Not affected if auth-required, no-privileged-accounts-exposed, versions-outside-range
Who cares fortiauthenticator, fortinet, identity, self-hosted
get system status8.0.0 through 8.0.3 and 6.6.0 through 6.6.10A use of externally-controlled format string vulnerability in Fortinet FortiAuthenticator 8.0.0 through 8.0.3, FortiAuthenticator 6.6.0 through 6.6.10 may allow an authenticated privileged attacker to execute unauthorized code or commands via http requests.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
Upgrade to 8.0.4 · 6.6.11
8.0.4 or above; 6.6.x to 6.6.11 or above