Unauthenticated RCE in Fortinet FortiOS and FortiSwitchManager CAPWAP daemon
CVE-2025-25249 is a heap-based buffer overflow in the cw_acd daemon responsible for CAPWAP processing in Fortinet FortiOS and FortiSwitchManager. A remote, unauthenticated attacker can trigger memory corruption through specially crafted CAPWAP control requests, potentially executing arbitrary code or commands. Affected releases include FortiOS 7.6.0–7.6.3, 7.4.0–7.4.8, 7.2.0–7.2.11, 7.0.0–7.0.17, all FortiOS 6.4 releases, and FortiSwitchManager 7.2.0–7.2.6 and 7.0.0–7.0.5. Affected FortiSASE deployments are also identified. ASLR and PIE increase exploitation complexity and preparation requirements. Active exploitation has deployed the PivotC2 remote-access trojan.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits unauthorized code or command execution in the affected service's security context, compromising device confidentiality, integrity, and availability. A compromised appliance can expose firewall and VPN configurations, stored credentials, pre-shared keys, and internal network information; support unauthorized policy changes; and provide a foothold for internal-network access. Observed PivotC2 deployments have enabled configuration and credential harvesting, interactive shells, traffic tunneling, network scanning, lateral movement, and data exfiltration. Memory corruption can also crash the affected service or disrupt device operation.
If you can’t patch tonight, do this now.
Until upgrades are complete, remove the fabric service from the allowaccess configuration on every interface. Where fabric access must remain enabled, apply local-in policies on each relevant interface to permit CAPWAP-CONTROL traffic on UDP ports 5246–5249 only from explicitly trusted device addresses and deny all other sources. Prioritize externally reachable deployments and monitor for unexpected processes, configuration changes, unauthorized accounts, suspicious outbound connections, and tunneling activity.
Patch, then assume compromise.
Upgrade FortiOS to 7.6.4, 7.4.9, 7.2.12, or 7.0.18 or later within the corresponding release branch, following Fortinet's supported upgrade path. Migrate all FortiOS 6.4 installations to a supported fixed release; FortiOS 6.4.17 was removed from the vendor's fixed-version list and must not be treated as a remediation. Upgrade FortiSwitchManager to 7.2.7 or 7.0.6 or later within the corresponding branch. Apply the applicable FortiSASE updates specified in Fortinet advisory FG-IR-25-084. Investigate potentially exposed devices for compromise: patching does not remove an existing implant. Rebuild confirmed compromised devices on fixed firmware, rotate potentially exposed administrative, VPN, LDAP, and wireless credentials and keys, and investigate possible internal-network intrusion.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
109 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.