Quick answers
- Is CVE-2025-53521 exploited in the wild?
- Yes. CVE-2025-53521 is known to be exploited in the wild, first recorded on 27 March 2026. Treat it as urgent.
- How severe is CVE-2025-53521?
- Critical severity, with a CVSS score of 9.8, published 15 October 2025.
- Which products and versions are affected?
- F5 Big-Ip Access Policy Manager 15.1.0 to 15.1.10.7, 16.1.0 to 16.1.6.0, 17.1.0 to 17.1.2, 17.5.0 to 17.5.1.2.
- Is there a fix for CVE-2025-53521?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-53521 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-53521?
- Check whether you run F5 BIG-IP or F5 Big-Ip Access Policy Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stack-based buffer overflow (CWE-121) exists in F5 BIG-IP when an Access Policy Manager (APM) policy is configured on a virtual server. The vulnerability is triggered by processing specific malicious network traffic, allowing an unauthenticated remote attacker to execute arbitrary code with high privileges. This flaw has been observed in active exploitation. Patches are available in versions 15.1.10.8, 16.1.6.1, 17.1.3, and 17.5.1.3; users are advised to update immediately or apply vendor-recommended mitigations.
Affected products
- F5 BIG-IP Access Policy Manager (APM) 15.1.0 to 15.1.10.7, 16.1.0 to 16.1.6.0, 17.1.0 to 17.1.2, 17.5.0 to 17.5.1.2
Timeline
- 2026-03-27: advisory: Initial publication and CISA KEV addition
- 2026-03-27: exploited: Confirmed active exploitation in the wild