F5 BIG-IP iRule Declarative API Causing TMM Memory Leak
CVE-2025-54805 Published on October 15, 2025
TMM Vulnerability
When an iRule is configured on a virtual server via the declarative API, upon re-instantiation, the cleanup process can cause an increase in the Traffic Management Microkernel (TMM) memory resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Vulnerability Analysis
CVE-2025-54805 can be exploited with network access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity, and a high impact on availability.
Weakness Type
What is a Memory Leak Vulnerability?
The software does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is often triggered by improper handling of malformed data or unexpectedly interrupted sessions. In some languages, developers are responsible for tracking memory allocation and releasing the memory. If there are no more pointers or references to the memory, then it can no longer be tracked and identified for release.
CVE-2025-54805 has been classified to as a Memory Leak vulnerability or weakness.
Products Associated with CVE-2025-54805
stack.watch emails you whenever new vulnerabilities are published in F5 Networks or F5 Networks Big Ip. Just hit a watch button to start following.
Affected Versions
F5 BIG-IP Next SPK:- Version 2.0.0 and below * is unaffected.
- Version 1.7.0 and below * is affected.
- Version 2.0.0 and below * is unaffected.
- Version 1.1.0 and below * is affected.
- Version 2.0.0 and below 2.1.0 is affected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.