Authentication Lockout Bypass via Race Condition in FortiAnalyzer and FortiManager
CVE-2026-22629 is an improper restriction of excessive authentication attempts vulnerability in Fortinet FortiAnalyzer, FortiAnalyzer Cloud, FortiManager, and FortiManager Cloud. According to the provided content, affected versions include FortiAnalyzer 7.6.0 through 7.6.4 and all versions in the 7.4, 7.2, 7.0, and 6.4 branches; FortiAnalyzer Cloud 7.6.0 through 7.6.4 and all versions in the 7.4, 7.2, 7.0, and 6.4 branches; FortiManager 7.6.0 through 7.6.4 and all versions in the 7.4, 7.2, 7.0, and 6.4 branches; and FortiManager Cloud 7.6.0 through 7.6.4 and all versions in the 7.4, 7.2, 7.0, and 6.4 branches. The flaw is classified as CWE-307 and stems from a race condition that allows an attacker to bypass brute-force protections and avoid intended authentication lockout behavior. The content indicates exploitation is possible by abusing a timing window in the authentication process, which increases practical attack complexity but may still permit repeated password-guessing attempts without triggering normal excessive-attempt restrictions.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.