Affects widely deployed FortiWeb WAF; auth bypass could enable credential access across many orgs.
CVE-2026-24017
Remote unauthenticated bypass of FortiWeb login rate limiting.
Is CVE-2026-24017 being exploited?
Not confirmed. CVE-2026-24017 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.76% probability of exploitation in the next 30 days.
How severe is CVE-2026-24017?
CVE-2026-24017 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-24017?
Yes. A fix has been recorded for CVE-2026-24017. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-24017 affect?
CVE-2026-24017 affects FortiWeb 8.0.0-8.0.2, FortiWeb 7.6.0-7.6.5, FortiWeb 7.4.0-7.4.10, FortiWeb 7.2.0-7.2.11, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-24017?
Apply vendor patch when released; restrict admin access; monitor login activity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remotely bypasses login rate limits to facilitate brute-force credential access against FortiWeb.
Patch when possible
- affected>= 8.0.0 and <= 8.0.2
- affected>= 7.6.0 and <= 7.6.5
- affected>= 7.4.0 and <= 7.4.10
- affected>= 7.2.0 and <= 7.2.11
- affected>= 7.0.0 and <= 7.0.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.