Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-59718: FortiCloud SSO SAML Authentication Bypass in Fortinet Products

Published Dec 9, 2025 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS9.8Critical · v3.1
EPSS68.1%99th percentile
CISA KEVYesAdded Dec 16, 2025
In the wildActivePer CISA KEV
Vendors
FortinetSiemens
IdentifiersCVE-2025-59718CWE-347 · Improper Verification of…

CVE-2025-59718 is an improper cryptographic signature verification vulnerability in the FortiCloud Single Sign-On authentication implementation of Fortinet FortiOS, FortiProxy, and FortiSwitchManager. An unauthenticated remote attacker can submit a crafted SAML response that is accepted without proper signature verification, bypassing administrative login authentication when FortiCloud SSO login is enabled. Affected releases are FortiOS 7.6.0–7.6.3, 7.4.0–7.4.8, 7.2.0–7.2.11, and 7.0.0–7.0.17; FortiProxy 7.6.0–7.6.3, 7.4.0–7.4.10, 7.2.0–7.2.14, and 7.0.0–7.0.21; and FortiSwitchManager 7.2.0–7.2.6 and 7.0.0–7.0.5. Exploitation in the wild is confirmed. The related FortiWeb vulnerability is tracked separately as CVE-2025-59719.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can provide unauthorized administrative access to affected security appliances. Attackers can use that access to create persistent administrator accounts, alter security and VPN settings, and export device configurations. Configuration disclosure can expose credentials and enterprise secrets that facilitate subsequent unauthorized access or lateral movement. These are consequences of administrative compromise; the vulnerability itself is an authentication bypass, not a demonstrated arbitrary-code-execution primitive.

Mitigation

If you can’t patch tonight, do this now.

Disable FortiCloud SSO administrative login until remediation is complete, or permanently if unnecessary. In System > Settings, switch 'Allow administrative login using FortiCloud SSO' to Off. The equivalent CLI configuration is: config system global; set admin-forticloud-sso-login disable; end. Explicitly inspect devices registered through the GUI because registration can enable this feature. Restrict administrative interfaces to trusted management networks or authorized hosts, and monitor for anomalous SSO logins, unexpected configuration exports, and unauthorized administrator creation.

Remediation

Patch, then assume compromise.

Upgrade using Fortinet's supported upgrade path to a current, non-affected release. The fixed releases for CVE-2025-59718 are FortiOS 7.6.4, 7.4.9, 7.2.12, and 7.0.18; FortiProxy 7.6.4, 7.4.11, 7.2.15, and 7.0.22; and FortiSwitchManager 7.2.7 and 7.0.6, or later non-affected releases in the corresponding branches. Also address subsequent FortiCloud SSO vulnerabilities, including CVE-2026-24858: malicious SSO activity on previously patched systems does not by itself establish a bypass of this specific fix. Where compromise is suspected, revoke administrative sessions, remove unauthorized accounts, validate configuration integrity, and rotate potentially exposed credentials and secrets. Patching alone does not remove established access or invalidate stolen credentials.

Public exploits

Exploits

4 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2025-59718-PoCThis repository provides operational exploit code for CVE-2025-59718, a critical authentication bypass vulnerability affecting several Fortinet products (FortiOS, FortiProxy, FortiSwitchManager, FortiWeb) when FortiCloud SSO is enabled. The exploit consists of two Python scripts: - 'poc.py': A minimal proof-of-concept that forges a SAMLResponse, base64-encodes it, and submits it to the target's '/remote/saml/login' endpoint. If successful, it grants admin access and prints session cookies for browser use. - 'advanced-poc.py': An enhanced, multithreaded version supporting bulk targeting (single, list, or file input), custom usernames, and endpoints. It writes results to a file and is suitable for scanning multiple devices in parallel. Both scripts exploit improper SAML response validation by Fortinet devices, allowing an attacker to impersonate an admin user and gain full administrative access. The attack is fully remote, requires no prior authentication, and targets the SAML login endpoint (typically '/remote/saml/login'). The payload is a crafted SAMLResponse XML asserting a 'super_admin' role, signed as if from 'https://sso.forticloud.com'. No hardcoded IPs or domains are present; the scripts require the attacker to specify the target(s). The only fingerprintable endpoints are the SAML login path and the SAML issuer/audience fields. The repository is well-structured, with clear separation between the minimal and advanced PoC scripts, and includes a README summarizing the vulnerability and affected products.exfil0 · Disclosed Dec 17, 2025 · python · networkOperationalAshwesker-CVE-2025-59718This repository contains a working proof-of-concept (PoC) exploit for CVE-2025-59718, a critical authentication bypass vulnerability in Fortinet products (FortiOS, FortiProxy, FortiSwitchManager) that use FortiCloud SSO. The exploit is implemented in a single Python script (CVE-2025-59718.py), which forges a malicious SAMLResponse XML payload impersonating an admin user. The script sends this payload to the target device's /remote/saml/login endpoint, exploiting improper SAML signature verification to gain administrative access without credentials. The README.md provides detailed vulnerability background, affected versions, mitigation advice, and usage instructions. The exploit is network-based, requires only the target's address, and if successful, returns a valid admin session cookie for further access. No detection or fake code is present; this is a real, functional exploit PoC.Ashwesker · Disclosed Dec 11, 2025 · python · markdown · networkPoCBlackash-CVE-2025-59718This repository contains a working proof-of-concept exploit for CVE-2025-59718, a critical authentication bypass vulnerability in Fortinet products (FortiOS, FortiProxy, FortiSwitchManager) that use FortiCloud SSO. The exploit is implemented in a single Python script (CVE-2025-59718.py) which forges a SAMLResponse XML, base64-encodes it, and submits it to the target's /remote/saml/login endpoint. If the target is vulnerable and FortiCloud SSO is enabled, the script grants the attacker full administrative access by bypassing authentication. The README.md provides detailed background, affected versions, mitigation advice, and usage instructions. The exploit is network-based, requires no credentials, and targets widely deployed enterprise security appliances. No hardcoded IPs or domains are used; the script takes a user-supplied target address. The main fingerprintable endpoints are the SAML login path and the SAML issuer/audience values used in the payload.Ashwesker · Disclosed Dec 11, 2025 · python · markdown · networkPoCSCTT-2026-33-0004-FortiCloud-SSO-Identity-SingularityRepository purpose: a Python proof-of-concept exploit named “SCTT-0004 VORTEX / SCTT-2026-33-0004” claiming a Fortinet/FortiCloud SSO “temporal session collision” that can bypass mitigations for CVE-2026-24858 by repeatedly interacting with the SSO login flow using precisely timed delays across 33 “layers.” Structure: - README.md: High-level claim and usage instructions (run script with <target> and <token>; oscillate for 33 layers). - SCTT-0004-VORTEX.py: Main exploit/PoC implementation. Creates a requests.Session with TLS verification disabled, computes per-layer timing (“temporal resonance”), crafts SAML-assertion-like data structures per layer (NameID, Conditions, AuthnStatement, Fortinet identity attributes), and drives a multi-request sequence intended to cause an identity/session privilege collision. Includes an interactive authorization prompt and prints results. - SCTT-2026-33-0004.json: Metadata describing the claimed vulnerability, mapping to CWE-288/CWE-347, affected versions, and references to CVE-2026-24858 and CVE-2025-59718. - LICENSE: MIT. Exploit capabilities (as implemented/claimed): - Remote, network-based interaction with a FortiCloud/Fortinet SSO endpoint. - Timing-based request orchestration over 33 iterations to attempt authentication bypass / privilege escalation via session-table “collision.” - Post-condition check by requesting an admin resource path to infer elevated access. Notable observables: - Hardcoded relative paths: /remote/saml/login and /admin/dashboard. - SAML/Fortinet attribute URNs embedded in the crafted assertion structure. - No hardcoded C2 infrastructure; target is user-supplied. The code is more consistent with a PoC than a fully weaponized module (no robust target fingerprinting, limited error handling shown in the provided excerpt, and no configurable payload beyond the request sequence).SimoesCTT · Disclosed Jan 31, 2026 · python · json · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortiosoperating_system
FortinetFortiproxyapplication
FortinetFortiswitchmanagerapplication
SiemensRuggedcom Ape1808 Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2025-59718 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Dec 16, 2025.
Is there a public exploit for CVE-2025-59718?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2025-59718, the earliest disclosed Dec 11, 2025.
Is there a patch for CVE-2025-59718?
Upgrade using Fortinet's supported upgrade path to a current, non-affected release. The fixed releases for CVE-2025-59718 are FortiOS 7.6.4, 7.4.9, 7.2.12, and 7.0.18; FortiProxy 7.6.4, 7.4.11, 7.2.15, and 7.0.22; and FortiSwitchManager 7.2.7 and 7.0.6, or later non-affected releases in the corresponding branches.
What products are affected by CVE-2025-59718?
Fortinet Fortios, Fortinet Fortiproxy, Fortinet Fortiswitchmanager, and Siemens Ruggedcom Ape1808 Firmware.
How severe is CVE-2025-59718?
CVE-2025-59718 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 68.1% (99th percentile) as of Nov 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity121Community discussion across Reddit, Mastodon, and other social sources.