CVE-2026-126244 · Infrastructure
NO FIX YET · SEE WHAT TO DO
FortiAuthenticator 8.0.0 through 8.0.3 and 6.6.0 through 6.6.10 lack limits on resource allocation. An unauthenticated attacker can exhaust system resources and knock the appliance offline.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
FortiAuthenticator appliances running 8.0.0 through 8.0.3 or 6.6.0 through 6.6.10 are in scope, and the NVD entry gives no further detail on which deployment or feature is needed. Teams running other FortiAuthenticator versions or no FortiAuthenticator can skip it.
Not affected if other-versions
Who cares fortiauthenticator, fortinet, self-hosted
A allocation of resources without limits or throttling 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 exhaust system resources, potentially resulting in a denial of service (DoS).
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.