Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Improper Cryptographic Signature Verification in Fortinet FortiOS, FortiSwitchMaster, FortiProxy, and FortiWeb (CVE‑2025‑59718) Enables SSO Bypass

Fortinet’s FortiOS, FortiSwitchMaster, FortiProxy and FortiWeb contain a signature‑verification flaw (CVE‑2025‑59718) that can let an unauthenticated attacker bypass FortiCloud SSO. The issue underscores the need for robust authentication controls and prompt patching to maintain audit‑ready evidence.

Verisq™ Intelligence · 📅 October 07, 2026 · 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
2 recommended
📰
Source
nvd.nist.gov

Improper Cryptographic Signature Verification in Fortinet FortiOS, FortiSwitchMaster, FortiProxy, and FortiWeb (CVE‑2025‑59718) Enables SSO Bypass

What It Is — Fortinet’s FortiOS, FortiSwitchMaster, FortiProxy and FortiWeb contain an improper verification of cryptographic signatures that can allow an unauthenticated attacker to bypass FortiCloud SSO login by sending a crafted SAML assertion. The flaw is tracked as CVE‑2025‑59718.

Exploitability — No public exploit code has been released, but the vulnerability is exploitable remotely without authentication. Fortinet’s advisory assigns a CVSS v3.1 base score of 8.8 (High).

Affected Products — FortiOS (various versions), FortiSwitchMaster, FortiProxy, FortiWeb.

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for continuous verification that authentication mechanisms (SAML, SSO) are correctly implemented and monitored.
  • Highlights the importance of timely patch management as evidence of due‑diligence in a vendor‑risk program.
  • A successful bypass would undermine the integrity of access‑control logs, eroding audit‑ready evidence for regulators and auditors.

Recommended Actions

  1. Apply the Fortinet security patches referenced in the advisory immediately.
  2. Validate SAML configuration and signature verification on all Fortinet appliances.
  3. Update your identity‑and‑access‑management (IAM) policies to require multi‑factor authentication for any SSO path.
  4. Capture remediation evidence (patch version, configuration snapshots) for audit purposes.

Source: CISA KEV – CVE‑2025‑59718

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2025-59718 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →