FortiWeb is a widely deployed enterprise WAF; unauthenticated GUI/CLI access grants full device control and can undermine web defenses across organizations.
CVE-2026-26035
Auth bypass in FortiWeb allows remote unauthenticated login to GUI/CLI.
Is CVE-2026-26035 being exploited?
Not confirmed. CVE-2026-26035 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.65% probability of exploitation in the next 30 days.
How severe is CVE-2026-26035?
CVE-2026-26035 is rated Critical with a CVSS score of 9.8. 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-26035?
Yes. A fix has been recorded for CVE-2026-26035. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26035 affect?
CVE-2026-26035 affects Fortinet FortiWeb 8.0.0 - 8.0.2, Fortinet FortiWeb 7.6.0 - 7.6.6, Fortinet FortiWeb 7.4.0 - 7.4.11, Fortinet FortiWeb 7.2.0 - 7.2.12, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26035?
Isolate management interfaces, restrict admin access via ACL/VPN, enable MFA, monitor logs; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote login to FortiWeb GUI/CLI; attackers can change configs, disable WAF protections, access data, and pivot into networks.
Immediate action required
- affected>= 8.0.0 and <= 8.0.2
- affected>= 7.6.0 and <= 7.6.6
- affected>= 7.4.0 and <= 7.4.11
- affected>= 7.2.0 and <= 7.2.12
- affected>= 7.0.0 and <= 7.0.12
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.