Secuno
ENNL
Book demo

CVE-2026-24017

Fortinet FortiWeb authentication bypass

8.1 HIGHEPSS 0.79%
  1. Published10 Mar 2026

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Fortinet FortiWeb≥ 7.0.0 < 7.0.12 · ≥ 7.2.0 < 7.2.12 · ≥ 7.4.0 < 7.4.11 · ≥ 7.6.0 < 7.6.6

Remediation

Fixed in
Fortinet FortiWeb≥ 7.0.12

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-74028.1
Improper Control of Interaction Frequency vulnerability in MeWare Software Development…
CVE-2026-327298.1
Runtipi is a personal homeserver orchestrator. Prior to 4.8.1, The Runtipi…
CVE-2025-543219.8
In Ascertia SigningHub through 8.6.8, there is a lack of rate limiting on the reset…

Frequently asked

Is CVE-2026-24017 being actively exploited?

CVE-2026-24017 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.79%.

How severe is CVE-2026-24017?

CVE-2026-24017 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.79% probability of exploitation.

Which products are affected by CVE-2026-24017?

Affected products include Fortinet FortiWeb.

How do I fix CVE-2026-24017?

Upgrade affected software to a fixed version, for example Fortinet FortiWeb 7.0.12 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-24017 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.