CVE-2025-59718

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

Detects exploitation of CVE-2025-59718, an improper verification of cryptographic signature vulnerability (CWE-347) affecting multiple Fortinet products. This vulnerability, listed in CISA's Known Exploited Vulnerabilities catalog, allows attackers to bypass signature validation checks, potentially enabling unsigned firmware/software installation, man-in-the-middle attacks on update channels, or code execution with elevated privileges on affected Fortinet appliances.

Vulnerability Intelligence

KEV — Known Exploited

Affected Software

Vendor
Fortinet
Product
Multiple Products

Weakness (CWE)

Timeline

Disclosed
December 16, 2025

CVSS

Unscored
Write-up coming soon

What is CVE-2025-59718 Fortinet Multiple Products Improper Verification of Cryptographic Signature (CVE-2025-59718)?

Fortinet Multiple Products Improper Verification of Cryptographic Signature (CVE-2025-59718) (CVE-2025-59718) maps to the Initial Access and Persistence and Defense Evasion tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for Fortinet Multiple Products Improper Verification of Cryptographic Signature (CVE-2025-59718), covering the data sources and telemetry it touches: CommonSecurityLog, Syslog, AzureNetworkAnalytics_CL. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Persistence Defense Evasion
Microsoft Sentinel / Defender
kusto
let FortinetManagementIPs = dynamic([]);
let SuspiciousFirmwareKeywords = dynamic(['unsigned', 'signature', 'bypass', 'invalid cert', 'certificate error', 'verification failed', 'sig check']);
union 
    (
        CommonSecurityLog
        | where DeviceVendor =~ "Fortinet"
        | where DeviceEventClassID has_any ("update", "firmware", "upgrade", "install")
        | where Message has_any (SuspiciousFirmwareKeywords)
        | extend EventType = "FirmwareUpdateAnomaly"
    ),
    (
        Syslog
        | where ProcessName has_any ("fortigate", "fortios", "fortid", "fgd", "fnbamd")
        | where SyslogMessage has_any (SuspiciousFirmwareKeywords)
        | extend EventType = "SyslogSignatureBypass"
    ),
    (
        AzureNetworkAnalytics_CL
        | where SrcIP_s in (FortinetManagementIPs) or DestIP_s in (FortinetManagementIPs)
        | where L7Protocol_s in~ ("https", "http")
        | where DestPort_d in (80, 443, 8443)
        | where FlowStatus_s !~ "Allowed"
        | extend EventType = "FortinetNetworkAnomaly"
    )
| summarize Count=count(), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by EventType, Computer, SourceIP=coalesce(SourceIP, SrcIP_s), DeviceVendor
| where Count > 1
| extend AlertSeverity = "High"
| project-reorder LastSeen, EventType, Computer, SourceIP, Count, AlertSeverity

Detects anomalous firmware/software update events on Fortinet devices where cryptographic signature verification may have failed or been bypassed, as well as suspicious syslog messages from Fortinet processes indicating signature check failures.

critical severity medium confidence

Data Sources

CommonSecurityLog Syslog AzureNetworkAnalytics_CL

Required Tables

CommonSecurityLog Syslog AzureNetworkAnalytics_CL

False Positives

  • Legitimate firmware upgrades on Fortinet appliances that generate verbose logging about signature checks
  • Internal vulnerability scanners probing Fortinet management interfaces
  • Network monitoring tools generating signature-related log noise during routine health checks

Sigma rule & cross-platform mapping

The detection logic for Fortinet Multiple Products Improper Verification of Cryptographic Signature (CVE-2025-59718) (CVE-2025-59718) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: network_connection
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate Fortinet Firmware Signature Bypass via Invalid Update Request

    Expected signal: HTTP 400 or 403 response from Fortinet API with error body referencing signature validation failure; corresponding event in Fortinet system logs with type=event subtype=update level=alert

  2. Test 2Fortinet Management Interface Signature-Related Error Log Injection Test

    Expected signal: Three syslog events appearing in SIEM with Fortinet device name, event type 'update' or 'system', and messages containing 'signature verification failed', 'cert verification failed', and 'unsigned firmware'

  3. Test 3Network-Level Simulation of Fortinet Update Channel Interception

    Expected signal: Network flow logs showing Fortinet appliance connecting to update server via proxy; Fortinet logs showing certificate validation errors or signature failures when intercepted responses are presented

Unlock Pro Content

Get the full detection package for CVE-2025-59718 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections