VulnTideExploited vulnerabilities, by vendor. Data as of .
Not in CISA KEVReported exploited: VulnCheck KEV since Published CVSS 9.1 criticalEPSS 29.2% probability of exploitation in 30 days
Fortinet

CVE-2025-59719: An improper verification of cryptographic signature vulnerability in Fortinet FortiWeb 8.0.0, FortiWeb 7.6.0 through…

Is it exploited?

Reported, not confirmed by CISA. VulnCheck KEV lists it as exploited in the wild. CISA has not added it to its Known Exploited Vulnerabilities catalog as of .

VulnCheck KEV lists it since . It cites 11 public reports, the first from .

How likely is exploitation in the next 30 days?
29.2%

EPSS score, percentile 98.2 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?
9.1 Critical

CVSS v3.1 base score, given by the CNA

What should I do?

Upgrade to FortiSwitchManager version 7.2.7 or above Upgrade to FortiSwitchManager version 7.0.6 or above Upgrade to FortiProxy version 7.6.4 or above Upgrade to … Full textSolution from the CVE record.

CISA has set no required action, because the vulnerability is not in KEV.

The CVE record links no vendor advisory, patch or mitigation.

Which versions are affected?

Affected

  • 8.0.0
  • 7.6.0 through 7.6.4
  • 7.4.0 through 7.4.9

Versions by product

Source: CISA KEV 2026.10.29, as of ; VulnCheck KEV, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.

Description

An improper verification of cryptographic signature vulnerability in Fortinet FortiWeb 8.0.0, FortiWeb 7.6.0 through 7.6.4, FortiWeb 7.4.0 through 7.4.9 may allow an unauthenticated attacker to bypass the FortiCloud SSO login authentication via a crafted SAML response message.

Source: CVE List, as of . About the data.

What to do

Advisories and patches

The CVE record links no vendor advisory, patch or mitigation.

Solution (from the CVE record)

Upgrade to FortiSwitchManager version 7.2.7 or above Upgrade to FortiSwitchManager version 7.0.6 or above Upgrade to FortiProxy version 7.6.4 or above Upgrade to FortiProxy version 7.4.11 or above Upgrade to FortiProxy version 7.2.15 or above Upgrade to FortiProxy version 7.0.22 or above Upgrade to FortiOS version 7.6.4 or above Upgrade to FortiOS version 7.4.9 or above Upgrade to FortiOS version 7.2.12 or above Upgrade to FortiOS version 7.0.18 or above Upgrade to FortiWeb version 8.0.1 or above Upgrade to FortiWeb version 7.6.5 or above Upgrade to FortiWeb version 7.4.10 or above Fortinet remediated this issue in FortiSASE version 25.3.b and hence customers do not need to perform any action. Upgrade to FortiPAM version 1.8.0 or above

This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Versions by product, as listed in the CVE record (1 product)
Fortinet FortiWeb
StatusVersions
Affected8.0.0
Affected7.6.0 through 7.6.4
Affected7.4.0 through 7.4.9

Versions not listed are: unaffected.

Source: CVE List, as of . About the data.

Weakness

CWE-347

CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record.

Timeline

DateEvent
CVE record published
CVE record last updated

References

1

Known exploited Fortinet vulnerabilities

  • CVE-2025-61624: Fortinet Multiple Products Path Traversal Vulnerability (added )
  • CVE-2026-104286: Fortinet FortiMail Path Traversal Vulnerability (added )
  • CVE-2025-25249: Fortinet Multiple Products Heap-based Buffer Overflow Vulnerability (added )
  • CVE-2025-68686: Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability (added )
  • CVE-2026-25089: Fortinet FortiSandbox OS Command Injection Vulnerability (added )