NETWORK INCIDENTS

Exploited now

Remediation guide
Fortinet · Multiple Products

CVE-2025-25249

Heap-based buffer overflow in cw_acd daemon

CISA KEV
Known exploitedadded 9 Sep 2026; US federal deadline 12 Sep 2026
Exploit likelihood
3.7%90th percentile · FIRST EPSS, 2026-11-15
Severity
8.1 HighCVSS 3, Fortinet
Last verified
30 Oct 2026against the sources below

1In plain language

A heap-based buffer overflow in the cw_acd daemon of FortiOS and FortiSwitchManager may let a remote attacker who hasn't logged in run arbitrary code or commands, through specially crafted requests.

Fortinet notes that security controls such as ASLR and PIE considerably raise the complexity and preparation effort needed.

Fortinet's advisory (last updated 23 Feb 2026) still shows Known Exploited: No; CISA added it to its Known Exploited Vulnerabilities catalog on 9 Sep 2026. Ransomware use: unknown.

Fortinet rates the impact as executing unauthorized code or commands.

CISA's entry also names FortiSASE. Fortinet's advisory lists only FortiOS and FortiSwitchManager.

2Am I affected?

Fortinet's table below lists, for each FortiOS and FortiSwitchManager branch, the affected versions and the solution.

Affected releases are summarised by release train in the Fix table.

Check your version

A command to show the running version: Not stated by vendor.

Any action for FortiSASE: Not stated by vendor.

3Fix

Fortinet says to follow the recommended upgrade path using its upgrade tool. FortiOS 6.4 has no fixed release: migrate to a fixed release. Source ↗

Fortinet first listed FortiOS 6.4.17 as fixed, then removed it on 23 Feb 2026, so 6.4.17 is not a fix.

VersionAffectedSolution
FortiOS 7.67.6.0 through 7.6.3Upgrade to 7.6.4 or above
FortiOS 7.47.4.0 through 7.4.8Upgrade to 7.4.9 or above
FortiOS 7.27.2.0 through 7.2.11Upgrade to 7.2.12 or above
FortiOS 7.07.0.0 through 7.0.17Upgrade to 7.0.18 or above
FortiOS 6.46.4 all versionsMigrate to a fixed release
FortiSwitchManager 7.27.2.0 through 7.2.6Upgrade to 7.2.7 or above
FortiSwitchManager 7.07.0.0 through 7.0.5Upgrade to 7.0.6 or above

4Can't patch tonight?

Fortinet's first workaround: for each interface, remove "fabric" access. For example, change this:

config system interface
    edit "port1"
        set allowaccess fabric ssh https
    next
end

Lines to look for in the running configuration, as the vendor shows them.

to this:

config system interface
    edit "port1"
        set allowaccess ssh https
    next
end

Lines to look for in the running configuration, as the vendor shows them.

Or disallow access to the capwap daemon: for each interface with the "fabric" service, block CAPWAP-CONTROL access to ports 5246 to 5249 through a local-in policy. Fortinet's example uses port1 as the interface where fabric is enabled and my_allowed_addresses for the devices allowed to reach CAPWAP:

config firewall service custom
    edit "CAPWAP-CONTROL"
        set udp-portrange 5246-5249
    next
end
config firewall addrgrp
edit "CAPWAP_DEVICES_IPs"
set member "my_allowed_addresses"
end
config firewall local-in-policy
    edit 1 (allow from trusted devices)
        set intf "port1" (where fabric is enabled)
        set srcaddr "CAPWAP_DEVICES_IPs"
        set dstaddr "all"
        set service "CAPWAP-CONTROL"
        set schedule "always"
        set action accept
    next
    edit 2 (block everyone else)
        set intf "port1" (where fabric is enabled)
        set srcaddr "all'
        set dstaddr "all"
        set service "CAPWAP-CONTROL"
        set schedule "always"
        set action deny
    next
end

Lines to look for in the running configuration, as the vendor shows them.

Fortinet's example has a mismatched quote in edit 2 (srcaddr "all' should be "all"), and its "(allow from trusted devices)" and "(where fabric is enabled)" notes are comments, not part of the commands. Fortinet doesn't say what else relies on fabric access on an interface: check before removing it, or use the local-in policy option instead. Workarounds reduce exposure; upgrading is the fix. our analysis

5Was I hit?

Logs to check, detection steps and indicators of compromise: Not stated by vendor.

CISA's catalog flags this CVE for forensic triage, and its required action points to CISA's BOD 26-04 guidance and its Forensics Triage Requirements. Source ↗

6Sources

Summary of public vendor guidance. Verify against the vendor advisory before acting.

See CVE-2025-25249 in the exploited-now list (exploit likelihood, CISA's description, deadline).

More Fortinet guides