CVE-2026-22629: An improper restriction of excessive authentication attempts vulnerability in Fortinet FortiAnalyzer 7.6.0...
An improper restriction of excessive authentication attempts vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4 all versions, FortiAnalyzer 7.2 all versions, FortiAnalyzer 7.0 all versions, FortiAnalyzer 6.4 all versions, FortiAnalyzer Cloud 7.6.0 through 7.6.4, FortiAnalyzer Cloud 7.4 all versions, FortiAnalyzer Cloud 7.2 all versions, FortiAnalyzer Cloud 7.0 all versions, FortiAnalyzer Cloud 6.4 all versions, FortiManager 7.6.0 through 7.6.4, FortiManager 7.4 all versions, FortiManager 7.2 all versions, FortiManager 7.0 all versions, FortiManager 6.4 all versions, FortiManager Cloud 7.6.0 through 7.6.4, FortiManager Cloud 7.4 all versions, FortiManager Cloud 7.2 all versions, FortiManager Cloud 7.0 all versions, FortiManager Cloud 6.4 all versions may allow an attacker to bypass bruteforce protections via exploitation of race conditions. The latter raises the complexity of practical exploitation.
Security readout for executives and security teams
Plain-English summary
This is a low-severity Fortinet authentication-control issue. In affected FortiAnalyzer and FortiManager deployments, an unauthenticated attacker may bypass brute-force protections through race conditions, potentially increasing password-guessing risk. Practical exploitation is described as complex, and the documented impact is limited confidentiality exposure.
Executive priority
Handle through normal vulnerability management with moderate attention if management interfaces are exposed. The business risk is credential-attack enablement against security management platforms, but public evidence provided here indicates low severity, high exploitation complexity, and no confirmed active exploitation.
Technical view
CVE-2026-22629 is CWE-307 in FortiAnalyzer, FortiAnalyzer Cloud, FortiManager, and FortiManager Cloud across listed 6.4 through 7.6 releases. The CVSS v3.1 score is 3.4: network reachable, high attack complexity, no privileges, no user interaction, low confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is most relevant where affected FortiAnalyzer or FortiManager administrative authentication endpoints are reachable by untrusted networks. Cloud variants are also listed. Organizations should map exact product and version inventory against Fortinet advisory FG-IR-26-079 and the CVE record.
Exploitation context
The bundle does not show CISA KEV listing or source evidence of active exploitation. The CVSS vector marks attack complexity high, and Fortinet's description says race-condition exploitation raises practical difficulty. Treat it as a hardening and lifecycle remediation item, not an emergency breach indicator from these sources alone.
Researcher notes
The key research angle is the race-condition bypass of brute-force protections, not direct authentication bypass. Sources do not provide implementation detail, fixed versions, or safe reproduction guidance. Avoid assuming broader Fortinet products are affected beyond the listed FortiAnalyzer and FortiManager families.
Mitigation direction
Review Fortinet advisory FG-IR-26-079 for supported remediation guidance.
Apply Fortinet-supported upgrades or fixes for affected versions once confirmed.
Restrict administrative login access to trusted networks where feasible.
Monitor administrative authentication logs for unusual failed-login patterns.
Enforce strong administrative authentication controls already supported in your environment.
Validation and detection
Inventory FortiAnalyzer, FortiAnalyzer Cloud, FortiManager, and FortiManager Cloud versions.
Compare deployed versions against the affected ranges in the CVE record.
Confirm whether administrative interfaces are reachable from untrusted networks.
Review authentication logs for abnormal repeated failures or timing anomalies.
Track Fortinet advisory updates for exact fixed-release guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-307: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-307 · source CWE mapping
Improper Restriction of Excessive Authentication Attempts
Improper Restriction of Excessive Authentication Attempts represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.