BIG-IP: Missing Release of Memory after Effective Lifetime
CVE-2025-61974 is a high-severity missing release of memory after effective lifetime vulnerability in BIG-IP from F5, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 17.5.1.3, 17.1.3, 16.1.6.1 as the first without the flaw, so updating BIG-IP to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update BIG-IP to 17.5.1.3 or 17.1.3 or 16.1.6.1 or 15.1.10.8, whichever matches your release line, or a later version.
- Read the advisory on my.f5.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| F5 | BIG-IP | 17.5.0 up to, but not including, 17.5.1.3; 17.1.0 up to, but not including, 17.1.3; 16.1.0 up to, but not including, 16.1.6.1; 15.1.0 up to, but not including, 15.1.10.8 | 17.5.1.3, 17.1.3, 16.1.6.1, 15.1.10.8 |
| F5 | BIG-IP Next SPK | 2.0.0 and later; 1.9.0 and later; 1.8.0 and later; 1.7.0 and later | Not stated |
| F5 | BIG-IP Next CNF | 2.0.0 and later; 1.1.0 and later | Not stated |
| F5 | BIG-IP Next for Kubernetes | 2.0.0 and later | Not stated |
| F5 | Big-ip Next Cloud-native Network Functions | 1.1.0 through 1.4.1; 2.0.0 through 2.1.0 | Not stated |
| F5 | Big-ip Next Service Proxy For Kubernetes | 1.7.0 through 1.9.2; 2.0.0 through 2.0.2 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (f5.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (f5.com) |
| CVSS 3.1 | 7.5 | High | CNA (f5.com) |
Official description
When a client SSL profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Release of Memory after Effective Lifetime
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
How developers prevent this class of flaw
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC). To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
More Missing Release of Memory after Effective Lifetime vulnerabilities (CWE-401)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in BIG-IP
- 9.8 Critical severity
F5 BIG-IP APM Heap-based Buffer Overflow Exploited
- 8.8 High severity
- 7.5 High severity
- 8.7 High severity
- 8.7 High severity
- 7.5 High severity
Recent Missing Release of Memory after Effective Lifetime vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 8.6 High severity
- 8.6 High severity
- 7.5 High severity
Spotted an error? Tell us.