Critical Auth Bypass Vulnerabilities in Fortinet Products Under Active Exploitation (CVE-2025-59718 & CVE-2025-59719)

Executive Summary

On December 9th, Fortinet’s PSIRT team publicly released an advisory to address critical authentication bypass vulnerabilities (CVE-2025-59718 and CVE-2025-59719) in multiple Fortinet products (FortiOS, FortiProxy, FortiSwitchManager, and FortiWeb) when FortiCloud single sign-on (SSO) is enabled. Soon after, on December 16th, Beazley Security Labs became aware of active exploitation of these vulnerabilities. CISA has also added both CVEs to the Known Exploited Vulnerabilities (KEV) index.

The vulnerabilities are remotely exploitable authentication bypass bugs, meaning they can be used by a threat actor to gain initial access to an organization’s network. CVE-2025-59718 and CVE-2025-59719 allow an attacker to bypass the FortiCloud SSO authentication "via a crafted SAML message." It's important to note that FortiCloud SSO login is not enabled by default, however, registering a Fortinet device with FortiCare will enable this feature unless explicitly disabled. Due to this, Beazley Security believes many Fortinet devices may be vulnerable without the administrator’s knowledge.

Beazley Security is aware of active exploitation of these vulnerabilities in the wild. Given the potential for further compromise once initial access has been granted to the Fortinet device, Beazley Security strongly recommends that affected organizations apply available patches immediately or disable FortiCloud SSO until patches can be applied.

Affected Systems and Products

Version

Affected

Solution

FortiOS 7.6

7.6.0 through 7.6.3

Upgrade to 7.6.4 or above

FortiOS 7.4

7.4.0 through 7.4.8 Upgrade to 7.4.9 or above

FortiOS 7.2

7.2.0 through 7.2.11 Upgrade to 7.2.12 or above

FortiOS 7.0

7.0.0 through 7.0.17 Upgrade to 7.0.18 or above

FortiOS 6.4

Not affected Not Applicable

FortiProxy 7.6

7.6.0 through 7.6.3 Upgrade to 7.6.4 or above

FortiProxy 7.4

7.4.0 through 7.4.10 Upgrade to 7.4.11 or above

FortiProxy 7.2

7.2.0 through 7.2.14 Upgrade to 7.2.15 or above

FortiProxy 7.0

7.0.0 through 7.0.21 Upgrade to 7.0.22 or above

FortiSwitchManager 7.2

7.2.0 through 7.2.6 Upgrade to 7.0.22 or above

FortiSwitchManager 7.0

7.0.0 through 7.0.5 Upgrade to 7.0.6 or above

FortiWeb 8.0

8.0.0 Upgrade to 8.0.1 or above

FortiWeb 7.6

7.6.0 through 7.6.4 Upgrade to 7.6.5 or above

FortiWeb 7.4

7.4.0 through 7.4.9 Upgrade to 7.4.10 or above

FortiWeb 7.2

Not affected Not Applicable

FortiWeb 7.0

Not affected Not Applicable

Mitigations and Workarounds

Patches have been released, and Beazley Security recommends that patches be applied immediately for any impacted appliances. If patches cannot be applied, Fortinet recommends temporarily disabling FortiCloud SSO on affected systems until they can be updated to reduce risk of compromise:

To disable FortiCloud SSO admin logins:

  1. Go to System -> Settings -> Switch.
  2. Change "Allow administrative login using FortiCloud SSO" to Off.

Or type the following command in the CLI:

config system global
set admin-forticloud-sso-login disable
end

Patches

The FortiGuard advisory recommends using their provided upgrade tool to update software on the affected products.

Indicators of Compromise (IOCs)

IOCs have been collected from Arctic Wolf and are presented here for convenience:

IOC 

Hosting Provider 

45.32.153[.]218

The Constant Company llc

167.179.76[.]111

The Constant Company llc

199.247.7[.]82

The Constant Company llc

45.61.136[.]7

Bl Networks

38.54.88[.]203

Kaopu Cloud Hk Limited

38.54.95[.]226

Kaopu Cloud Hk Limited

38.60.212[.]97

Kaopu Cloud Hk Limited

149.104.121[.]141

Cogent Communications, LLC

198.98.54[.]209

FranTech Solutions

According to the article from Arctic Wolf, the following logs were observed during attack:

  • Malicious logins were typically observed against the admin account:

date=2025-12-12 time=REDACTED devname=REDACTED devid=REDACTED eventtime=REDACTED tz=REDACTED logid="0100032001" type="event" subtype="system" level="information" vd="root" logdesc="Admin login successful" sn=REDACTED user="admin" ui="sso(199.247.7[.]82)" method="sso" srcip=199.247.7[.]82 dstip=REDACTED action="login" status="success" reason="none" profile="super_admin" msg="Administrator admin logged in successfully from sso(199.247.7[.]82)"

  • Following malicious SSO logins, configurations were exported to the same IP addresses via the GUI interface:

date=2025-12-12 time=REDACTED devname=REDACTED devid=REDACTED eventtime=REDACTED tz=REDACTED logid="0100032095" type="event" subtype="system" level="warning" vd="root" logdesc="Admin performed an action from GUI" user="admin" ui="GUI(199.247.7[.]82)" action="download" status="success" msg="System config file has been downloaded by user admin via GUI(199.247.7[.]82)"

Technical Details

Details on the vulnerabilities provided by Fortinet are limited at the time of this writing. CVE-2025-597198 and CVE-2025-59719 stem from improper verification of cryptographic signatures in the FortiCloud SSO SAML authentication flow across multiple Fortinet products.

If affected Fortinet devices are configured to use FortiCloud SSO, an attacker can leverage crafted SAML messages to bypass authentication checks, potentially gaining unauthenticated administrative access.

Although FortiCloud SSO login is disabled in the default factory settings, registering a device via FortiCare on setup will enable FortiCloud SSO when registration occurs, unless explicitly disabled on the registration page.

Arctic Wolf has reportedly observed exploitation of these authentication bypass vulnerabilities in the wild, with threat actors conducting malicious FortiCloud SSO admin attacks to gain initial access into environments.

How Beazley Security is Responding

Beazley Security is monitoring client perimeter devices through our Exposure Management Platform to identify impacted devices and support organizations in remediation of any issues found.

We are also conducting threat hunts across our MDR environment to detect potential exploitation attempts against our clients.

If you believe your organization may have been impacted by this attack campaign and need support, please contact our Incident Response team.

Sources

Aware of an incident impacting your industry? Let us know:

Report an incident