FortiwebApplication · Fortinet
CVE-2026-24017
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn Improper Control of Interaction Frequency (CWE-799) vulnerability in FortiWeb allows remote unauthenticated attackers to bypass authentication rate-limits through crafted requests. This enables potential brute-force attacks against login endpoints, with success dependent on attacker resources and target password complexity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FortiwebApplication
>= 7.0.0, < 7.0.12>= 7.2.0, < 7.2.12>= 7.4.0, < 7.4.11>= 7.6.0, < 7.6.6>= 8.0.0, < 8.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check FortiWeb versionRun the command to display the FortiWeb system status and locate the firmware version field. Compare this version number against the affected ranges: 7.0.0 to 7.0.11, 7.2.0 to 7.2.11, 7.4.0 to 7.4.10, 7.6.0 to 7.6.5, and 8.0.0 to 8.0.2.Affected if The installed version falls within any of these ranges.
-
Identify exposed authentication endpointsReview the FortiWeb deployment configuration and network topology to determine whether the login or authentication pages are accessible from untrusted networks (such as the internet). Check firewall policies, VIP mappings, or reverse proxy settings that route external traffic to FortiWeb login endpoints.Affected if Login pages or authentication APIs are directly reachable from unauthenticated/untrusted networks.
-
Verify rate-limiting configurationInspect the FortiWeb rate-limiting or brute-force protection settings via the web UI or CLI to confirm whether authentication rate limits are currently enabled for the login endpoints.Affected if Rate-limiting is disabled or not applied to the authentication endpoints.
-
Review authentication logs for attack patternsExamine FortiWeb authentication and access logs for signs of multiple failed login attempts from the same source within short time windows, or patterns indicating the rate limit is being circumvented.Affected if Logs show high volumes of login attempts from single sources that appear to bypass configured rate limits.
You are affected if your FortiWeb version is in the listed ranges AND your login endpoints are externally accessible, regardless of whether rate limiting is configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.0.127.2.127.4.11
Upgrade FortiWeb to vendor-patched versions. As an immediate compensating control, implement additional rate-limiting at upstream firewalls or load balancers to protect the authentication endpoints.
Upgrade to 7.0.12 (for 7.0.x), 7.2.12 (for 7.2.x), 7.4.11 (for 7.4.x), or 7.6.6 (for 7.6.x) - recommended: 7.6.6 or later
- 1. Identify the currently installed FortiWeb version using the CLI command: get system status or via the web UI under System > Status
- 2. Determine which version branch your current installation belongs to (7.0.x, 7.2.x, 7.4.x, or 7.6.x)
- 3. Download the appropriate fixed firmware version from Fortinet Customer Support portal: https://support.fortinet.com/
- 4. Upload the firmware file via FortiWeb web UI (System > Maintenance > Firmware > Upload) or CLI: execute restore system config
- 5. Back up the current configuration using: execute backup full-config
- 6. After firmware upload, reboot the device and verify the new version is running: get system status
- 7. Verify the rate-limit bypass is mitigated by confirming authentication rate-limiting functions correctly under System > Security > Authentication > Rate Limit Policy
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiweb
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data