CVE-2025-64446
Fortinet FortiWeb Path Traversal Vulnerability
Fortinet FortiWeb
A relative path traversal vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.1, FortiWeb 7.6.0 through 7.6.4, FortiWeb 7.4.0 through 7.4.9, FortiWeb 7.2.0 through 7.2.11, FortiWeb 7.0.0 through 7.0.11 may allow an attacker to execute administrative commands on the system via crafted HTTP or HTTPS requests.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 14 November 2025. US federal agencies were required to remediate it by 21 November 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 91.1%, which is higher than 99.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2025-64446 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-64446.
What does CVE-2025-64446 affect?
CVE-2025-64446 affects Fortinet FortiWeb. A relative path traversal vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.1, FortiWeb 7.6.0 through 7.6.4, FortiWeb 7.4.0 through 7.4.9, FortiWeb 7.2.0 through 7.2.11, FortiWeb 7.0.0 through 7.0.11 may allow an attacker to execute administrative commands on the system via crafted HTTP or HTTPS requests.
How severe is CVE-2025-64446?
CVE-2025-64446 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 91.1%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 21 November 2025.
How should organisations respond to CVE-2025-64446?
Apply the vendor patch for Fortinet FortiWeb as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.