Called exploited 6 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing6d
- Last KEV listing1d
- Last sighting7mo
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Dec 16, 2025
- EUVDENISA, European Unionlisted Dec 16, 2025
- VulnCheck KEVcommercial researchlisted Dec 15, 2025
- CIRCLaggregator, mirrors the abovelisted Dec 16, 2025, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.levelblue.com/blogs/spiderlabs-blog/ttp-briefing-q2-2026
- reported exploitationblog.qualys.com/vulnerabilities-threat-research/2026/07/08/f
- reported exploitationctrlaltintel.com/research/Qilin/
- reported exploitationwww.trendmicro.com/vinfo/gb/security/news/cybercrime-and-dig
- reported exploitationwww.rapid7.com/blog/post/ve-fortigate-cve-2025-59718-exploit
- reported exploitationblackpointcyber.com/wp-content/uploads/2026/04/2026-Annual-T
19 public reports collected from VulnCheck and CIRCL, first on Dec 15, 2025. Each links to its original source. We have not verified them.
Description
Fortinet FortiOS, FortiSwitchMaster, FortiProxy, and FortiWeb contain an improper verification of cryptographic signature vulnerability that may allow an unauthenticated attacker to bypass the FortiCloud SSO login authentication via a crafted SAML message. Please be aware that CVE-2025-59719 pertains to the same problem and is mentioned in the same vendor advisory. Ensure to apply all patches mentioned in the advisory.
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
