TMM memory exhaustion via unreleased cleanup resources
Published Oct 15, 2025 · Updated Oct 15, 2025
Memory exhaustion in F5 BIG-IP Next products allows remote authenticated users to interrupt TMM traffic processing via the declarative API. The cleanup path used when re-instantiating a virtual server with an iRule fails to release memory after its effective lifetime, increasing TMM memory utilization. The attacker needs low-privilege API access and the affected iRule configuration; repeated re-instantiation can exhaust memory and disrupt dependent traffic services.
Summary
What happened
Memory exhaustion in F5 BIG-IP Next products allows remote authenticated users to interrupt TMM traffic processing via the declarative API. The cleanup path used when re-instantiating a virtual server with an iRule fails to release memory after its effective lifetime, increasing TMM memory utilization. The attacker needs low-privilege API access and the affected iRule configuration; repeated re-instantiation can exhaust memory and disrupt dependent traffic services.
The record
- CVE
- CVE-2025-54805
- Published
- Oct 15, 2025
- Updated
- Oct 15, 2025
- Vendor
- F5 Networks
- Product
- BIG-IP Next for Kubernetes
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 15, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo