IRONSMITHINTEL
CRITICALCVSS9.8
|
Actively Exploited
|CISA KEV|CVE-2025-59718|Auth: none — unauthenticated|Reboot: required|Manual only

Fortinet Multiple Products Improper Verification of Cryptographic Signature Vulnerability (CVE-2025-59718)

Fortinet FortiOS, FortiSwitchMaster, FortiProxy, and FortiWeb contain an improper verification of cryptographic signature vulnerability that may allow an unauthenticated attacker to bypass the FortiCloud SSO login authentication via a crafted SAML message. Please be aware that CVE-2025-59719 pertains to the same problem and is mentioned in the same vendor advisory. Ensure to apply all patches mentioned in the advisory.

Published Dec 9, 2025 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-12-23 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-347) (CWE-347) vulnerability in Fortinet Multiple Products. 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. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

→

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

●Network Security Team
●Firewall Administrators
●IT Security
●Running fortiproxy: 7.0.0 ≤ v < 7.0.22, 7.2.0 ≤ v < 7.2.15, 7.4.0 ≤ v < 7.4.11, 7.6.0 ≤ v < 7.6.4; fortiswitchmanager: 7.0.0 ≤ v < 7.0.6, 7.2.0 ≤ v < 7.2.7; fortios: 7.0.0 ≤ v < 7.0.18, 7.2.0 ≤ v < 7.2.12, 7.4.0 ≤ v < 7.4.9, 7.6.0 ≤ v < 7.6.4
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-12-16 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-12-23.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2025-59718's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2025-59718↗ MSRC Advisory↗ NVD↗ Vendor Advisory