Skip to main content
Report · SANS ISC Handlers DiaryAbout CVE-2025-64446Published

Honeypot: FortiWeb CVE-2025-64446 Exploits, (Sat, Nov 15th)

Source SANS ISC Handlers Diary

0
Compare
Authoritative record:CVE-2025-64446· Critical 9.4

Exploited in the wild · KEV due 21 Nov 2025 · public exploit available (Metasploit, Exploit-DB) : apply the vendor's fix or mitigations to affected systems now.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 14 Nov 2025

  2. Exploited in the wild: evidence found.

    Listed in CISA KEV the same day as disclosure

  3. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Fortinet, Inc.

    , 10 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 17 minutes after disclosure

  4. , the same day as disclosure

  5. KEV remediation due

    US federal deadline

    , 7 days after disclosure

  6. First Exploit-DB entry (opens in a new tab)

    Fortinet FortiWeb v8.0.1 - Auth Bypass +1 more

    , 143 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

AI-suggested

  1. Immediately audit FortiWeb devices for any unauthorized administrative accounts, especially newly created profiles matching the prof_admin pattern.
  2. Restrict management interface access to trusted IP addresses using network segmentation and firewall rules to limit exposure to the internet.
  3. Monitor network traffic for suspicious POST requests targeting FortiWeb endpoints, particularly those matching the exploit patterns reported in honeypots.
  4. Implement strict logging and alerting on administrative account creation and configuration changes within FortiWeb appliances.
  5. Apply vendor patches or firmware updates as soon as they become available to remediate CVE-2025-64446.
  6. If patches are not yet available, consider temporary mitigations such as disabling vulnerable endpoints or deploying web application firewall rules to block exploit payloads.
  7. Conduct penetration testing and vulnerability scanning focused on FortiWeb devices to identify exposure and validate mitigations.
  8. Educate security teams about this vulnerability and ensure incident response plans include steps for FortiWeb compromise scenarios.
  9. Collaborate with Fortinet support and subscribe to threat intelligence feeds for updates on exploit activity and remediation guidance.

Description

Like many have reported, we too noticed exploit attempts for CVE-2025-64446 in our honeypots.

References

Community reviews

Loading reviews…