F5 BIG-IP Next CVE-2025-61974
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach TLS-terminating virtual server
-
DeliverySend undisclosed crafted requests
-
ExploitTrigger unreleased memory allocation (CWE-401)
-
ExecutionExhaust memory resources
-
ImpactDenial of service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Resource cleanup, leak prevention
|
| Exploitation Conditions | Requires that a client SSL profile be configured on a virtual server (i.e., the device is performing TLS termination for client-side connections) - without this configuration the vulnerable code path is not reached, so default/non-TLS-terminating deployments are not affected. When that condition is met, the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no user interaction, and low complexity are needed; the attacker only needs network reachability to the affected virtual server. The specific request content that triggers the leak is undisclosed by the vendor. Products past End of Technical Support were not evaluated, so EoTS versions are outside the assessed scope. |
| Impact | Signals are consistent and point to a moderate, availability-only risk rather than a top-tier emergency. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated condition, but impact is confined to availability (VA:H; VC:N/VI:N) - consistent with CWE-401 (missing memory release) causing memory exhaustion / denial of service, not code execution or data theft. The 8.7 score is driven entirely by that unauthenticated reachability plus high availability impact. Real-world urgency is tempered: EPSS is low at 0.46% (38th percentile), the CVE is not in CISA KEV, and no public POC is referenced, so this is 'no public exploit identified at time of analysis.' Note the tension between the high CVSS and the low EPSS/absence of KEV - the base score reflects worst-case reachability, while the exploitation probability signals this is not currently seeing opportunistic mass exploitation. One caveat: exploitation is gated on a specific configuration (a client SSL profile bound to a virtual server), which the CVSS base metrics do not capture - verify your deployment uses SSL termination before treating this as unconditionally remote-unauthenticated. The 'Information Disclosure' tag conflicts with the CVSS (VC:N) and CWE-401; this is a resource-exhaustion/DoS issue, not disclosure. |
| Exploit ScenarioDerived | An attacker who can reach a BIG-IP Next virtual server that is configured with a client SSL profile sends a stream of specially crafted (undisclosed) requests that each leak memory the system never reclaims. Sustained over time, memory utilization climbs until the data plane degrades or the service becomes unavailable. No authentication or user interaction is required, but no public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Uncontrolled memory consumption in F5 BIG-IP Next for Kubernetes, BIG-IP Next Cloud-Native Network Functions and BIG-IP Next Service Proxy for Kubernetes lets remote attackers steadily exhaust memory on an affected appliance or pod by sending undisclosed crafted requests to a virtual server that has a client SSL profile attached. The assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N, with C:N/I:N/A:H) means no credentials and no user interaction are required once the TLS-terminating virtual server is reachable over the network, and the leak accumulates across requests until the service degrades or becomes unavailable. No public exploit code has been identified at time of analysis, EPSS is a low 0.46% (38th percentile), and the issue is not in CISA KEV, so this reads as a moderate availability-only risk rather than an emergency.
RemediationAI
The provided data does not enumerate a specific fixed release, so the authoritative remediation is to consult F5 advisory K000156733 (https://my.f5.com/manage/s/article/K000156733) for the current patched build of BIG-IP Next for Kubernetes, BIG-IP Next Cloud-Native Network Functions and BIG-IP Next Service Proxy for Kubernetes, and upgrade any 2.0.0/2.1.0 or otherwise affected deployment; because EoTS releases were not evaluated, plan an upgrade to a supported branch rather than assuming an old build is unaffected. Where an immediate upgrade is not possible, the most effective compensating control is to eliminate the exposed configuration: unbind the client SSL profile from internet-facing virtual servers and terminate TLS upstream or downstream instead - the trade-off is a re-architecture of the traffic path and loss of BIG-IP-side TLS inspection. As a second control, restrict network reachability to virtual servers that carry a client SSL profile using network policy or firewall source-range allowlists so only trusted clients can generate requests - this shrinks the attacker pool but does not stop a permitted client from leaking memory. Third, instrument container/process memory metrics with alerting and set proactive pod restarts or replica recycling on memory thresholds to bound the blast radius - this only buys time, since each restart drops in-flight connections. Finally, apply per-source connection and request rate limits at the edge to slow leak accumulation, accepting that aggressive limits can throttle legitimate traffic.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-401, Missing Release of Memory after Effective Lifetime - a classic memory leak. The vulnerable code path sits in the client-side TLS handling of BIG-IP Next: a virtual server is only exposed when a client SSL profile is bound to it, i.e. when the device is terminating TLS for inbound client connections and therefore parsing attacker-supplied TLS and HTTP traffic in that context. Each triggering request allocates memory that is never returned to the allocator; because nothing in the vector requires authentication or interaction, an unauthenticated remote sender can repeat the request to drive steady growth in process memory until the data plane or pod is OOM-killed or begins refusing work. This affects the containerized/CNF delivery of BIG-IP Next rather than classic TMOS: CPE entries cover BIG-IP Next for Kubernetes (pinned at 2.0.0 and 2.1.0), BIG-IP Next Cloud-Native Network Functions and BIG-IP Next Service Proxy for Kubernetes (both wildcarded, so the precise affected release ranges are not enumerated in the CPE data and must be read from the vendor advisory). Notably, the supplied tags label this 'Information Disclosure', but the authoritative vector has C:N/I:N and A:H - confidentiality is not impacted and the practical consequence is denial of service through memory exhaustion, so the disclosure tag should be treated as inaccurate metadata. Versions past End of Technical Support were not evaluated by the vendor and are outside the assessed scope.
Know when Big Ip Next Service Proxy For Kubernetes gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Network-reachable, unauthenticated, no UI memory-leak DoS; only availability impacted (A:H), with C:N/I:N and no scope change, gated on an SSL-profile config that does not raise base complexity.
Primary rating from Vendor (f5).
CVSS VectorVendor: f5
DescriptionCVE.org
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.
Executive ViewAI
F5 BIG-IP Next for Kubernetes, BIG-IP Next Cloud-Native Network Functions, and BIG-IP Next Service Proxy for Kubernetes are affected by a high-severity memory exhaustion vulnerability (CVE-2025-61974) that can degrade or disrupt service availability. Organizations using these products for containerized networking and security functions should prioritize inventory and mitigation, as an unauthenticated remote attacker could repeatedly send crafted requests to a TLS-enabled virtual server to exhaust memory. While no public exploit identified at time of analysis or active exploitation has been reported, leadership should care because a successful attack could impact critical network services and application availability.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to virtual servers with client SSL profiles, implement rate limiting and memory monitoring with alerts, configure pod resource limits, and disable unnecessary client SSL profiles. Monitor vendor advisory for patch availability.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Affected Products (CPE)CVE.org
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
The BGP daemon (bgpd) in IP Infusion ZebOS through 7.10.6 allow remote attackers to cause a denial of service by sending
When a BIG-IP HTTP/2 httprouter profile is configured on a virtual server, undisclosed responses can cause an increase i
Denial of service in F5 BIG-IP Next Cloud-Native Network Functions and Service Proxy for Kubernetes allows unauthenticat
A use-after-free (CWE-416) in F5 BIG-IP's Traffic Management Microkernel (TMM) allows remote unauthenticated attackers t
Denial of service in F5 BIG-IP allows remote unauthenticated attackers to exhaust memory resources on virtual servers co
When SIP Session and Router ALG profiles are configured on a Message Routing type virtual server, undisclosed traffic ca
Denial of service in F5 BIG-IP allows remote, unauthenticated attackers to terminate the Traffic Management Microkernel
Denial of service in F5 BIG-IP Next deployments with HTTP/2 Ingress enabled allows unauthenticated network attackers to
When TCP profile with Multipath TCP enabled (MPTCP) is configured on a Virtual Server, undisclosed traffic along with co
When HTTP/2 is configured on BIG-IP or BIG-IP Next SPK systems, undisclosed responses can cause the Traffic Management M
When a client-side HTTP/2 profile and the HTTP MRF Router option are enabled for a virtual server, and an iRule using th
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB