# CVE-2026-24017: Security feature bypass in FortiWeb

> Remote attackers can bypass authentication rate limits in FortiWeb, facilitating brute-force attacks against user accounts.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/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:** 11 Mar 2026
- **Also known as:** GHSA-76jh-wm3g-gchp

## What is CVE-2026-24017?

CVE-2026-24017 is a high-severity vulnerability in Fortinet Fortiweb, 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 Control of Interaction Frequency vulnerability [CWE-799] vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.2, FortiWeb 7.6.0 through 7.6.5, FortiWeb 7.4.0 through 7.4.10, FortiWeb 7.2.0 through 7.2.11, FortiWeb 7.0.0 through 7.0.11 may allow a remote unauthenticated attacker to bypass the authentication rate-limit via crafted requests. The success of the attack depends on the attacker's resources and the password target complexity.

Weakness: CWE-799 (Improper Control of Interaction Frequency)

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

It affects 1 product.


Products: Fortinet Fortiweb.

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

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

## Is CVE-2026-24017 being exploited?

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

## Other vulnerabilities in Fortinet Fortiweb

- [CVE-2025-25257](https://insights.sbomify.com/CVE-2025-25257/): Fortinet FortiWeb SQL Injection (critical 9.6, exploited in the wild)
- [CVE-2025-64446](https://insights.sbomify.com/CVE-2025-64446/): Fortinet FortiWeb Path Traversal (critical 9.4, exploited in the wild)
- [CVE-2025-58034](https://insights.sbomify.com/CVE-2025-58034/): Fortinet FortiWeb OS Command Injection (medium 6.7, exploited in the wild)
- [CVE-2020-29015](https://insights.sbomify.com/CVE-2020-29015/): SQL injection in Fortinet FortiWeb (critical 9.8)
- [CVE-2020-29016](https://insights.sbomify.com/CVE-2020-29016/): Memory corruption in Fortinet FortiWeb (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24017 is a high-severity vulnerability in Fortinet Fortiweb, 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-24017 in the wild and no public exploit code.

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

## Sources

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

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