An unauthenticated heap overflow in the FortiOS CAPWAP daemon, patched in January 2026, is now being used to plant a remote-access trojan on FortiGate firewalls. CISA lists it as exploited; Fortinet’s advisory still does not.
Find your fixed versionFortinet advisory FG-IR-25-084 lists FortiOS 7.6.4, 7.4.9, 7.2.12 and 7.0.18 or later as fixed, and FortiSwitchManager 7.2.7 and 7.0.6 or later. FortiOS 6.4 has no fix: every 6.4 version is affected, so migrate to a fixed release.
CISA added CVE-2025-25249 to its Known Exploited Vulnerabilities catalog on September 9, 2026. SOCRadar reports exploitation since at least July 2026. If you are upgrading anyway, FortiOS 7.6.5 or 7.4.10 or later also fixes CVE-2025-61624, a second Fortinet flaw CISA added in October that has no fix on 7.2 or 7.0.
From Fortinet advisory FG-IR-25-084 (published January 13, 2026, last updated February 23, 2026).
| Product and branch | Affected | Fixed (Fortinet) | Notes |
|---|---|---|---|
| FortiOS 7.6 | 7.6.0 through 7.6.3 | 7.6.4 or above | 7.6.5 or above also fixes CVE-2025-61624. |
| FortiOS 7.4 | 7.4.0 through 7.4.8 | 7.4.9 or above | The exploit tool SOCRadar recovered targets 7.4.0 to 7.4.8 builds. 7.4.10 or above also fixes CVE-2025-61624. |
| FortiOS 7.2 | 7.2.0 through 7.2.11 | 7.2.12 or above | No 7.2 build fixes CVE-2025-61624; Fortinet says to migrate to a fixed release for that one. |
| FortiOS 7.0 | 7.0.0 through 7.0.17 | 7.0.18 or above | Same as 7.2: no 7.0 fix for CVE-2025-61624. |
| FortiOS 6.4 | All 6.4 versions | None | Migrate to a fixed release. Fortinet removed 6.4.17 from the fixed list on February 23, 2026. |
| FortiSwitchManager 7.2 | 7.2.0 through 7.2.6 | 7.2.7 or above | |
| FortiSwitchManager 7.0 | 7.0.0 through 7.0.5 | 7.0.6 or above |
Check your version from the CLI with the standard command get system status (the Version: line), or on the dashboard’s System Information widget. Plan the route with Fortinet’s upgrade path tool, as the advisory recommends.
The bug is in cw_acd, the FortiOS daemon that handles CAPWAP, the protocol a FortiGate uses to manage FortiAP access points.
Fortinet describes CVE-2025-25249 as a heap-based buffer overflow (CWE-122) in the FortiOS and FortiSwitchManager cw_acd daemon that may allow a remote unauthenticated attacker to execute arbitrary code or commands via specifically crafted requests. Fortinet adds that ASLR and PIE “considerably raise” the effort needed to exploit it.
SOCRadar’s analysis of the attackers’ exploit shows how they got past that: a CAPWAP discovery request to UDP port 5246 makes the daemon leak memory addresses, which defeats ASLR, and crafted CAPWAP messages then overflow the heap and launch a Node.js reverse shell. Node.js already ships with FortiOS, so nothing new has to be installed to run it.
Exposure depends on CAPWAP being reachable. Fortinet’s workarounds both target the same path: the fabric access service on an interface, and the CAPWAP control ports, UDP 5246 to 5249. An internet-facing interface with fabric in its allowaccess list is the case to fix first.
show system interface and look at each set allowaccess line. Any interface that lists fabric accepts CAPWAP control traffic. If it faces the internet and you can’t upgrade today, apply a workaround below.
Fortinet’s advisory says “Known Exploited: No”. CISA and SOCRadar say otherwise.
On September 8, 2026, the SOCRadar Threat Research Unit reported, with high confidence, active exploitation of CVE-2025-25249 since at least July 2026. Successful attacks install PivotC2, a Node.js remote-access trojan built for FortiGate firewalls. According to SOCRadar:
CISA added the flaw to its Known Exploited Vulnerabilities catalog on September 9, 2026, with a September 12 due date for US federal agencies. As of November 16, Fortinet’s advisory, last updated February 23, 2026, still shows “Known Exploited: No”. Go by CISA and the research, not that field.
Fortinet gives two. Both close the CAPWAP path; neither replaces the upgrade.
Fortinet’s example changes set allowaccess fabric ssh https on port1 to set allowaccess ssh https. But set allowaccess replaces the whole list, so pasting that onto a WAN port can switch on internet-facing SSH and HTTPS admin and drop services such as ping, fgfm or snmp. Use unselect instead, which removes only fabric:
config system interface
edit "port1"
unselect allowaccess fabric
next
end
If you use set allowaccess instead, list every service the interface already has, and don’t add ssh or https to an internet-facing port. If FortiAPs, FortiSwitches (FortiLink), FortiExtenders or downstream Security Fabric FortiGates connect through that interface, removing fabric cuts them off, so use Option 2 there.
For each interface with the fabric service, Fortinet blocks CAPWAP-CONTROL (UDP 5246 to 5249) with a local-in policy: policy 1 allows your trusted devices, policy 2 denies everyone else. The advisory’s example, lightly cleaned up for pasting (its inline notes removed and a stray quote mark fixed). Replace port1 and my_allowed_addresses with your interface and an address object for your access points and switches:
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"
next
end
config firewall local-in-policy
edit 1
set intf "port1"
set srcaddr "CAPWAP_DEVICES_IPs"
set dstaddr "all"
set service "CAPWAP-CONTROL"
set schedule "always"
set action accept
next
edit 2
set intf "port1"
set srcaddr "all"
set dstaddr "all"
set service "CAPWAP-CONTROL"
set schedule "always"
set action deny
next
end
Pick policy IDs that show firewall local-in-policy doesn’t already use. Local-in policies match top-down, so the allow policy must come before the deny. If an existing local-in policy already accepts this traffic, move the new policies above it. If any FortiAPs reach this interface over the internet (remote APs), their public IPs must be in my_allowed_addresses, or they go offline.
Fortinet’s advisory gives no indicators. These come from SOCRadar’s report.
Look for sessions to the two PivotC2 servers SOCRadar found, then for the staged payload and Node.js processes. The commands are SOCRadar’s (the first line clears any old session filter); if diagnose sys process list isn’t available on your build, try diagnose sys process pidof node:
diagnose sys session filter clear
diagnose sys session filter daddr 146.103.99.177
diagnose sys session list
diagnose sys session filter daddr 46.151.29.58
diagnose sys session list
fnsysctl ls -la /tmp/.i.js
fnsysctl ls -la /tmp/
diagnose sys process list | grep node
SOCRadar warns that Node.js legitimately ships with FortiOS, so a process name alone is not proof. The stager saves PivotC2 as /tmp/.i.js and runs it in the background. SOCRadar’s report also lists file hashes and two Tor bridge addresses the group used.
Two more Fortinet entries joined the Known Exploited Vulnerabilities catalog in October 2026.
| CVE and advisory | Issue | Affected | Fixed |
|---|---|---|---|
CVE-2025-61624FG-IR-26-122, CVSS 6.0 Published April 14, 2026; in CISA KEV since October 16, 2026 |
Path traversal in the command line interpreter. A privileged attacker can write or delete arbitrary files with crafted arguments to existing commands. Fortinet marks it known exploited. | FortiOS 7.6.0 to 7.6.4, 7.4.0 to 7.4.9, and all of 7.2, 7.0 and 6.4. Also FortiProxy, FortiPAM and FortiSwitchManager. | FortiOS 7.6.5 or 7.4.10 and above; 7.2, 7.0 and 6.4 must migrate to a fixed release. FortiProxy 7.6.5 or 7.4.12, FortiPAM 1.7.1, FortiSwitchManager 7.2.8 or 7.0.7 and above. A virtual patch (FG-VD-59270.0day) is in FMWP database update 25.120. |
CVE-2026-104286FG-IR-26-175, CVSS 9.8 Published October 1, 2026; in CISA KEV since October 1, 2026 |
FortiMail path traversal and NULL-byte handling. An unauthenticated attacker can write arbitrary files with crafted HTTP or HTTPS requests. Reported exploited in the wild. | FortiMail 8.0.0 to 8.0.1, 7.6.0 to 7.6.6, 7.4.0 to 7.4.8, 7.2.0 to 7.2.9, and all of 7.0. | 8.0.2, 7.6.7 or 7.4.9 and above; 7.2.10 and above (listed as upcoming at the advisory’s October 7 update); 7.0 must migrate. Workaround: turn off IBE (config system encryption ibe, set status disable). FortiMail Cloud was fixed by Fortinet on October 5. |
Fortinet’s second workaround uses the same FortiOS feature that keeps known attackers away from your VPN login.
A local-in policy filters traffic addressed to the FortiGate itself, before it reaches services such as CAPWAP or the SSL VPN. The FortiGate guide uses one with an IP threat feed as the source address: a deny policy in front of the SSL VPN or IPsec gateway drops listed IPs before the login page loads. That needs FortiOS 7.2.4 or later (or 7.4.0 or later); on 7.0 the guide uses a firewall policy instead. ThreatListPro is one such feed: 5.4M+ IPv4 addresses, built from real attacks on live production Palo Alto GlobalProtect VPN portals in the US and checked for new attackers every 6 hours.
That matters after an incident like this one. PivotC2 decrypts stored SSL VPN credentials, and guessed passwords are what VPN brute force runs on. Rotate them, require MFA, and cut down who can reach the login page.
It does not patch CVE-2025-25249 or any other flaw. ThreatListPro is a list of addresses seen attacking VPN logins, not of the addresses in this campaign, and an attacker using an address that isn’t on the list is not affected. It is IPv4 only. Upgrade FortiOS first, and use Fortinet’s workarounds for CAPWAP.
Yes. CISA added CVE-2025-25249 to its Known Exploited Vulnerabilities catalog on September 9, 2026. SOCRadar reports exploitation since at least July 2026 to install the PivotC2 remote-access trojan, with about 30,000 FortiGate addresses targeted and 178 devices infected. Fortinet’s advisory, last updated February 23, 2026, still says “Known Exploited: No”.
Fortinet lists FortiOS 7.6.4, 7.4.9, 7.2.12 and 7.0.18 or later as fixed, and FortiSwitchManager 7.2.7 and 7.0.6 or later. Every FortiOS 6.4 version is affected and has no fix, so migrate to a fixed release. FortiOS 7.6.5 or 7.4.10 or later also fixes CVE-2025-61624.
Fortinet gives two. Remove the fabric service from the allowaccess list of each interface, or, on interfaces that keep fabric, add local-in policies that allow CAPWAP-CONTROL (UDP 5246 to 5249) only from your trusted devices and deny everyone else. Neither replaces the upgrade.
Both appear. Fortinet rates CVE-2025-25249 8.1 (CVSS 3.1, attack complexity high) with a temporal score of 7.4. NVD rates it 9.8, scoring attack complexity as low.
No. SOCRadar says patching closes the entry point but does not remove an implant that is already running or undo credentials already taken. If you find signs of PivotC2, rebuild or restore the FortiGate from a known-good state and rotate every credential stored in its configuration.
CISA’s catalog entry names FortiOS, FortiSwitchManager and FortiSASE, but Fortinet’s advisory lists only FortiOS and FortiSwitchManager and gives no FortiSASE action. FortiSASE customers should ask Fortinet support.
ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours, in the plain-text format a FortiGate threat feed expects. Monthly is $19.99 with a 14-day free trial and no card needed.
Start a 14-day free trial Or test 200 entries first: free, no signupThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.
Continue with FortiGate hardening and the other current alerts.