# CVE-2026-22629: Race condition in FortiAnalyzer

> Attackers can bypass brute-force protections in FortiAnalyzer and FortiManager via race conditions, potentially enabling unauthorized access attempts.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/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
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-qwch-jrh6-94wh

## What is CVE-2026-22629?

CVE-2026-22629 is a low-severity vulnerability in Fortinet Fortianalyzer, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 4 products.


Products: Fortinet Fortianalyzer, Fortinet Fortianalyzer Cloud, Fortinet Fortimanager, Fortinet Fortimanager Cloud.

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

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

## Is CVE-2026-22629 being exploited?

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

## Other vulnerabilities in Fortinet Fortianalyzer

- [CVE-2026-24858](https://insights.sbomify.com/CVE-2026-24858/): Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel (critical 9.4, exploited in the wild)
- [CVE-2023-25610](https://insights.sbomify.com/CVE-2023-25610/): Memory corruption in FortiAnalyzer (critical 9.3)
- [CVE-2021-32603](https://insights.sbomify.com/CVE-2021-32603/): Server-side request forgery in Fortinet FortiAnalyzer, FortiManager (high 8.8)
- [CVE-2020-12817](https://insights.sbomify.com/CVE-2020-12817/): Cross-site scripting in Fortinet FortiAnalyzer (high 8.8)
- [CVE-2024-48886](https://insights.sbomify.com/CVE-2024-48886/): Auth bypass in FortiOS (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22629 is a low-severity vulnerability in Fortinet Fortianalyzer, published on 10 Mar 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-22629 in the wild and no public exploit code.

Affected product: Fortinet Fortianalyzer. 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-22629/ (Markdown: https://insights.sbomify.com/CVE-2026-22629/index.md)
```

## Sources

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

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