cve.bz

CVE-2025-59718 Fortinet Multiple Products Improper Verification of Cryptographic Signature Vulnerability

9.8 criticalKEVEPSS 68%

Critical (9.8) in Fortinet Multiple Products. In CISA KEV since 2025-12-16. EPSS 68% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
68% (unchanged from 68% a week ago; 68% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2025-12-16, due 2025-12-23
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2025-12-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-59718 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-59718?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-59718?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-59718 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Fortinet FortiSwitchManagerfrom 7.2.0 through 7.2.6
Fortinet FortiSwitchManagerfrom 7.0.0 through 7.0.5
Fortinet FortiOSfrom 7.6.0 through 7.6.3
Fortinet FortiOSfrom 7.4.0 through 7.4.8
Fortinet FortiOSfrom 7.2.0 through 7.2.11
Fortinet FortiOSfrom 7.0.0 through 7.0.17
Fortinet FortiProxyfrom 7.6.0 through 7.6.3
Fortinet FortiProxyfrom 7.4.0 through 7.4.10
Fortinet FortiProxyfrom 7.2.0 through 7.2.14
Fortinet FortiProxyfrom 7.0.0 through 7.0.21

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-25-135-01Siemens RUGGEDCOM APE1808 Devices2025-05-13Critical ManufacturingRUGGEDCOM APE1808none listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • exfil0/CVE-2025-59718-PoC Harbor Check: matches CVE 6 stars, Python, created
    Fortinet announced two closely related authentication‑bypass vulnerabilities on 9 December 2025. Both flaws involve improper verification o…
  • moften/CVE-2025-59718-Fortinet-Poc 3 stars, Python, created
    PoC para determinar si Fortinet es vulnerable a CVE-2025-59718 / CVE-2025-59719

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON