CVE-2025-53521: Unauthenticated Remote Code Execution in F5 BIG-IP APM
- Vendor
- F5
CVE-2025-53521 is an unauthenticated remote-code-execution vulnerability in F5 BIG-IP Access Policy Manager (APM), exposed when an APM access policy is configured on a virtual server. Specially crafted traffic sent to the virtual server can trigger the flaw in data-plane APM processing involving the apmd process. Affected releases are 17.5.0–17.5.1, 17.1.0–17.1.2, 16.1.0–16.1.6, and 15.1.0–15.1.10. Initially disclosed on October 15, 2025 as a denial-of-service issue, it was reclassified as actively exploited remote code execution in March 2026. Its historical weakness classification is CWE-770; the precise technical mechanism enabling code execution has not been publicly established. End-of-Technical-Support versions were not evaluated.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows unauthenticated code execution on an affected BIG-IP APM appliance, compromising the confidentiality, integrity, and availability of the device and potentially providing initial access to connected enterprise networks. Associated intrusions have involved in-memory web shells and persistent implants, including PoisonedRefresh, although the vulnerability is not established as the delivery mechanism in every investigated case. The originally documented denial-of-service impact includes TMM termination and restart, temporarily disrupting traffic handled by the appliance.
Mitigation
If you can’t patch tonight, do this now.
No confirmed workaround that prevents remote code execution is identified; prioritize patching. Review F5 compromise indicators, audit logs, suspicious local-user commands, SELinux changes, unexpected outbound HTTP/S traffic, executable integrity, and Apache/PHP process memory. Do not rely exclusively on filesystem scans or integrity-check results, because associated implants can operate in memory and interfere with integrity checking. High-availability clustering may reduce disruption from the originally documented process crashes but does not prevent code execution or compromise.
Remediation
Patch, then assume compromise.
Upgrade to BIG-IP 17.5.1.3, 17.1.3, 16.1.6.1, or 15.1.10.8, or a later vendor-confirmed fixed release for the applicable branch. Migrate unsupported releases to a supported, fixed version. Investigate potentially exposed appliances regardless of patch status: patching does not establish whether prior compromise occurred or remove existing implants. Preserve volatile evidence before disruptive changes, follow F5 compromise-assessment and recovery guidance, and isolate and rebuild compromised devices where necessary. These fixes address CVE-2025-53521, not the separate CVE-2026-94127 vulnerability.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-53521 exploited in the wild?
- Yes. As of Oct 29, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 27, 2026.
- Is there a public exploit for CVE-2025-53521?
- As of Oct 29, 2026, Mallory has found no public exploit for CVE-2025-53521.
- Is there a patch for CVE-2025-53521?
- Upgrade to BIG-IP 17.5.1.3, 17.1.3, 16.1.6.1, or 15.1.10.8, or a later vendor-confirmed fixed release for the applicable branch. Migrate unsupported releases to a supported, fixed version.
- What products are affected by CVE-2025-53521?
- F5 Big-Ip Access Policy Manager, F5 Big-Ip Aam, F5 BIG-IP Advanced Firewall Manager, F5 Big-Ip Advanced Web Application Firewall, F5 Big-Ip Analytics, and at least 15 more.
- How severe is CVE-2025-53521?
- CVE-2025-53521 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 2.3% (84th percentile) as of Oct 29, 2026.
Recent activity
214 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.