Skip to content
VulniPulse
Critical9.1Fortinet Exploited CISA KEV

Critical [CVE-2025-59718 +1] improper verification of cryptographic signature vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through…

This critical-severity Fortinet advisory covers CVE-2025-59718 and CVE-2025-59719 affecting FortiOS, FortiProxy, FortiWeb.

CVE-2025-59718 Published Dec 9, 2025Updated by vendor Jul 14, 2026
Affected products & platforms
FortinetFortiGateFirewallFortiOSFortiWebFortiProxyFortiSwitch
Open vendor advisory

Android app · Google Play

Monitor future Fortinet CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A improper verification of cryptographic signature vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through 7.4.8, FortiOS 7.2.0 through 7.2.11, FortiOS 7.0.0 through 7.0.17, FortiProxy 7.6.0 through 7.6.3, FortiProxy 7.4.0 through 7.4.10, FortiProxy 7.2.0 through 7.2.14, FortiProxy 7.0.0 through 7.0.21, FortiSwitchManager 7.2.0 through 7.2.6, FortiSwitchManager 7.0.0 through 7.0.5 allows an unauthenticated attacker to bypass the FortiCloud SSO login authentication via a crafted SAML response message.

Affected products named by the advisory: FortiWeb.

CISA Known Exploited Vulnerability

Listed:
Dec 16, 2025 · federal remediation due Dec 23, 2025
Required action:
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Ransomware use:
Unknown

KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.

Affected versions
  • FortiOS 7.6: 7.6.0 through 7.6.3
  • FortiOS 7.4: 7.4.0 through 7.4.8
  • FortiOS 7.2: 7.2.0 through 7.2.11
  • FortiOS 7.0: 7.0.0 through 7.0.17
  • FortiProxy 7.6: 7.6.0 through 7.6.3
  • FortiProxy 7.4: 7.4.0 through 7.4.10
  • FortiProxy 7.2: 7.2.0 through 7.2.14
  • FortiProxy 7.0: 7.0.0 through 7.0.21
  • FortiSwitchManager 7.2: 7.2.0 through 7.2.6
  • FortiSwitchManager 7.0: 7.0.0 through 7.0.5
  • FortiWeb 8.0: 8.0.0
  • FortiWeb 7.6: 7.6.0 through 7.6.4
  • FortiWeb 7.4: 7.4.0 through 7.4.9

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Fixed versions
  • FortiOS 7.6: 7.6.4
  • FortiOS 7.4: 7.4.9
  • FortiOS 7.2: 7.2.12
  • FortiOS 7.0: 7.0.18
  • FortiProxy 7.6: 7.6.4
  • FortiProxy 7.4: 7.4.11
  • FortiProxy 7.2: 7.2.15
  • FortiProxy 7.0: 7.0.22
  • FortiSwitchManager 7.2: 7.2.7
  • FortiSwitchManager 7.0: 7.0.6
  • FortiWeb 8.0: 8.0.1
  • FortiWeb 7.6: 7.6.5
  • FortiWeb 7.4: 7.4.10

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade per the Affected/Solution table: FortiOS 7.6: 7.6.4; FortiOS 7.4: 7.4.9; FortiOS 7.2: 7.2.12; FortiOS 7.0: 7.0.18; FortiProxy 7.6: 7.6.4; ….
Temporary workarounds
  • To prevent being affected by this vulnerability on vulnerableversions, please turn off the FortiCloud login feature (if enabled) temporarily untilupgrading to a non-affected version.To turn off FortiCloud login, go to System -> Settings -> Switch"Allow administrative login using FortiCloud SSO" to Off.
  • Or type thefollowing command in the CLI:
  • config system global set admin-forticloud-sso-login disableend

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.