dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Dec 2025.
FortiproxyApplication · Fortinet

CVE-2025-59718

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 7.0.6 / 7.0.18 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an improper verification of cryptographic signature vulnerability in FortiOS, FortiProxy, and FortiSwitchManager that allows an unauthenticated attacker to bypass FortiCloud SSO login authentication by sending a crafted SAML response message. The vulnerability stems from the system failing to properly validate the cryptographic signature on SAML assertions, enabling authentication bypass.

MitigationUpgrade FortiOS to version 7.4.9 or later (7.4.x), 7.2.12 or later (7.2.x), 7.0.18 or later (7.0.x), or 7.6.4 or later (7.6.x); upgrade FortiProxy to version 7.4.11 or later (7.4.x), 7.2.15 or later (7.2.x), 7.0.22 or later (7.0.x), or 7.6.4 or later (7.6.x); and upgrade FortiSwitchManager to version 7.2.7 or later (7.2.x) or 7.0.6 or later (7.0.x).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortiproxyApplication
Affected:>= 7.0.0, < 7.0.22>= 7.2.0, < 7.2.15>= 7.4.0, < 7.4.11>= 7.6.0, < 7.6.4
FortiswitchmanagerApplication
Affected:>= 7.0.0, < 7.0.6>= 7.2.0, < 7.2.7
FortiosOperating system
Affected:>= 7.0.0, < 7.0.18>= 7.2.0, < 7.2.12>= 7.4.0, < 7.4.9>= 7.6.0, < 7.6.4
Ruggedcom Ape1808 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify product and version
    Log into the Fortinet device CLI and run `get system status` to display the firmware version and product name
    Affected if The product is FortiOS, FortiProxy, or FortiSwitchManager and the version is within the affected ranges: FortiProxy 7.0.0-7.0.21, 7.2.0-7.2.14, 7.4.0-7.4.10, 7.6.0-7.6.3; FortiSwitchManager 7.0.0-7.0.5, 7.2.0-7.2.6; FortiOS 7.0.0-7.0.17, 7.2.0-7.2.11, 7.4.0-7.4.8, 7.6.0-7.6.3
  2. Verify SAML SSO configuration
    In the device GUI, navigate to User & Authentication > SAML SSO, or run `get system saml` in the CLI to display SAML settings
    Affected if SAML-based FortiCloud SSO is enabled or configured on the device
  3. Check FortiCloud SSO status
    In the GUI, go to System > FortiCloud and inspect whether SSO login is active, or review authentication policy settings for FortiCloud integration
    Affected if FortiCloud SSO authentication is currently active or pending configuration on the device

You are affected if the device runs an affected version of FortiOS, FortiProxy, or FortiSwitchManager AND has SAML-based FortiCloud SSO authentication enabled or configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.6 / 7.0.18 / 7.0.22 or later
Fixed in 7.0.67.0.187.0.22
Interim mitigation

Upgrade FortiOS to version 7.4.9 or later (7.4.x), 7.2.12 or later (7.2.x), 7.0.18 or later (7.0.x), or 7.6.4 or later (7.6.x); upgrade FortiProxy to version 7.4.11 or later (7.4.x), 7.2.15 or later (7.2.x), 7.0.22 or later (7.0.x), or 7.6.4 or later (7.6.x); and upgrade FortiSwitchManager to version 7.2.7 or later (7.2.x) or 7.0.6 or later (7.0.x).

Recommended fix High confidence

FortiOS: 7.0.18+, 7.2.12+, 7.4.9+, 7.6.4+ | FortiProxy: 7.0.22+, 7.2.15+, 7.4.11+, 7.6.4+ | FortiSwitchManager: 7.0.6+, 7.2.7+

  1. 1. Identify the Fortinet product (FortiOS, FortiProxy, or FortiSwitchManager) currently deployed in your environment
  2. 2. Determine the currently installed version using the CLI command: 'get system status' or via the web UI under Dashboard > Status
  3. 3. For FortiOS: upgrade to 7.0.18 or later for 7.0.x builds; 7.2.12 or later for 7.2.x builds; 7.4.9 or later for 7.4.x builds; 7.6.4 or later for 7.6.x builds
  4. 4. For FortiProxy: upgrade to 7.0.22 or later for 7.0.x builds; 7.2.15 or later for 7.2.x builds; 7.4.11 or later for 7.4.x builds; 7.6.4 or later for 7.6.x builds
  5. 5. For FortiSwitchManager: upgrade to 7.0.6 or later for 7.0.x builds; 7.2.7 or later for 7.2.x builds
  6. 6. Download the appropriate firmware from Fortinet Customer Support portal or FortiGuard
  7. 7. Back up the current configuration before applying the upgrade
  8. 8. Upload and install the firmware via the web UI (System > Firmware) or CLI: 'execute firmware upgrade'
Caveat Standard minor version upgrades within the same major branch typically have minimal compatibility impact; review Fortinet release notes for any configuration changes or deprecated features before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortiproxy Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59718 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data