Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-53521: CWE-770 Allocation of Resources Without Limits or Throttling in F5 BIG-IP

0
High
VulnerabilityCVE-2025-53521cvecve-2025-53521cwe-770
Published: Wed Oct 15 2025 (10/15/2025, 13:55:52 UTC)
Source: CVE Database V5
Vendor/Project: F5
Product: BIG-IP

Description

CVE-2025-53521 is a high-severity vulnerability in F5 BIG-IP devices where the Traffic Management Microkernel (TMM) can be terminated due to resource exhaustion when an Access Policy Manager (APM) Access Policy is configured on a virtual server. The flaw arises from allocation of resources without proper limits or throttling, leading to denial of service. It affects multiple recent BIG-IP versions (15. 1. 0, 16. 1. 0, 17. 1. 0, 17. 5.

AI-Powered Analysis

AILast updated: 10/23/2025, 01:03:43 UTC

Technical Analysis

CVE-2025-53521 is a vulnerability classified under CWE-770 (Allocation of Resources Without Limits or Throttling) affecting F5 BIG-IP devices, specifically when an Access Policy Manager (APM) Access Policy is configured on a virtual server. The vulnerability allows an attacker to send specially crafted, undisclosed traffic to the BIG-IP system, causing the Traffic Management Microkernel (TMM) process to terminate unexpectedly. TMM is a core component responsible for managing network traffic and enforcing policies on BIG-IP devices. Its termination results in denial of service (DoS), disrupting network traffic management and potentially causing downtime for services relying on the BIG-IP appliance. The vulnerability affects multiple actively supported versions of BIG-IP (15.1.0, 16.1.0, 17.1.0, and 17.5.0), excluding versions that have reached End of Technical Support (EoTS). The CVSS v3.1 base score is 7.5, indicating a high severity with network attack vector, no required privileges or user interaction, and impact limited to availability (no confidentiality or integrity loss). No public exploits or active exploitation have been reported yet. The root cause is the lack of resource allocation limits or throttling mechanisms in the APM Access Policy configuration, allowing resource exhaustion through crafted traffic. This vulnerability can be leveraged remotely by unauthenticated attackers, making it a significant risk for organizations using BIG-IP devices for access management and traffic control.

Potential Impact

For European organizations, the impact of CVE-2025-53521 can be substantial, particularly for those relying on F5 BIG-IP appliances for secure remote access, load balancing, and traffic management. The termination of the TMM process leads to denial of service, potentially causing outages of critical applications, disruption of remote access services, and interruption of business operations. This can affect sectors such as finance, healthcare, government, and telecommunications, where BIG-IP devices are commonly deployed. The lack of confidentiality or integrity impact means data breaches are unlikely, but availability loss can lead to operational downtime, financial losses, and reputational damage. Additionally, critical infrastructure providers using BIG-IP for secure access policies could face increased risk of service disruption, which may have cascading effects on public services. The ease of exploitation without authentication increases the threat level, especially if attackers scan for vulnerable devices exposed to the internet or internal networks.

Mitigation Recommendations

1. Monitor network traffic to detect unusual or high-volume traffic patterns targeting BIG-IP virtual servers configured with APM Access Policies. 2. Restrict access to BIG-IP management and virtual server interfaces using network segmentation, firewalls, and access control lists to limit exposure to untrusted networks. 3. Apply rate limiting or traffic shaping on ingress points to prevent resource exhaustion from undisclosed traffic patterns. 4. Stay informed of F5’s official security advisories and apply patches or updates promptly once released for this vulnerability. 5. Implement redundancy and failover mechanisms for BIG-IP devices to minimize service disruption in case of TMM termination. 6. Conduct regular security assessments and penetration testing focusing on BIG-IP configurations and access policies. 7. Disable or reconfigure APM Access Policies where not strictly necessary to reduce attack surface. 8. Use logging and alerting features to detect TMM process crashes or restarts to enable rapid incident response.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
f5
Date Reserved
2025-10-03T23:04:38.083Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68efa99327d7577a18004061

Added to database: 10/15/2025, 2:02:59 PM

Last enriched: 10/23/2025, 1:03:43 AM

Last updated: 11/28/2025, 6:40:30 PM

Views: 67

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats