Skip to main content

Fortinet FortiOS CVE-2025-59718

CRITICAL
Improper Verification of Cryptographic Signature (CWE-347)
2025-12-09 psirt@fortinet.com
9.8
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Analysis Generated
Jun 09, 2026 - 10:32 vuln.today
Added to CISA KEV
Jun 09, 2026 - 10:31 CISA
CVE Published
Dec 09, 2025 - 18:15 nvd
CRITICAL 9.8

DescriptionCVE.org

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.

AnalysisAI

Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to defeat FortiCloud SSO login by submitting a crafted SAML response, due to improper verification of the response's cryptographic signature. The flaw is confirmed actively exploited (CISA KEV), with Arctic Wolf observing malicious SSO logins in the wild, and EPSS rates it at the 93rd percentile of likelihood. Combined with a 9.8 CVSS score and CWE-347 root cause, this is a top-priority patching target for any organization running affected Fortinet management planes.

Technical ContextAI

The vulnerability lives in the SAML-based FortiCloud Single Sign-On flow used by FortiOS, FortiProxy, and FortiSwitchManager management interfaces. CWE-347 (Improper Verification of Cryptographic Signature) indicates the service processes SAML assertions without correctly validating the issuer's signature - common implementation defects in this class include accepting unsigned assertions, honoring attacker-chosen signing keys, mishandling XML canonicalization, or failing signature validation while still consuming the asserted identity. SAML responses carry the authenticated subject and group claims, so a forged or tampered assertion lets the attacker impersonate any FortiCloud-linked identity. The 'Jwt Attack' tag from the intelligence feed suggests token-level forgery techniques (such as algorithm confusion or key substitution) are involved in observed exploitation.

RemediationAI

Patch available per vendor advisory - apply the fixed builds documented in Fortinet PSIRT FG-IR-25-647 (https://fortiguard.fortinet.com/psirt/FG-IR-25-647) for each affected branch of FortiOS, FortiProxy, and FortiSwitchManager; consult the advisory for the exact target build per release train rather than relying on third-party version claims. Until patching is complete, disable FortiCloud SSO on management interfaces and revert to local administrator authentication, which removes the vulnerable SAML code path at the cost of breaking centralized identity workflows. Additionally restrict administrative interface exposure to a management VLAN or trusted-IP allowlist (trunk-link only) so unauthenticated internet attackers cannot reach the SAML endpoint, accepting that this complicates legitimate remote admin access. Review SSO and admin login logs for suspicious authentications consistent with Arctic Wolf's observations (https://arcticwolf.com/resources/blog/arctic-wolf-observes-malicious-sso-logins-following-disclosure-cve-2025-59718-cve-2025-59719/) and rotate administrative credentials and API tokens on any device that was internet-exposed before patching. Confirm KEV due-date compliance via the CISA catalog entry: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-59718.

CVE-2013-3900 MEDIUM
5.5 Dec 11

Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update

CVE-2026-48558 CRITICAL POC
9.5 Jun 12

Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke

CVE-2025-25291 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2025-25292 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2022-25898 CRITICAL POC
9.8 Jul 01

The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT

CVE-2024-42004 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti

CVE-2024-41145 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27

CVE-2024-41138 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work

CVE-2024-45409 CRITICAL POC
9.8 Sep 10

The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t

CVE-2022-35929 CRITICAL POC
9.8 Aug 04

cosign is a container signing and verification utility. Rated critical severity (CVSS 9.8), this vulnerability is remote

CVE-2022-31053 CRITICAL POC
9.8 Jun 13

Biscuit is an authentication and authorization token for microservices architectures. Rated critical severity (CVSS 9.8)

CVE-2021-43572 CRITICAL POC
9.8 Nov 09

The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1 fails to

Share

CVE-2025-59718 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy