F5 BIG-IP CVE-2025-61990
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach BIG-IP data plane over network
-
DeliverySend undisclosed crafted traffic
-
ExploitTrigger double-free in TMM
-
ExecutionTMM process terminates
-
ImpactTraffic processing disrupted (DoS)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Double free prevention
|
| Exploitation Conditions | Exploitation requires that the BIG-IP system runs on a multi-bladed chassis platform with more than one blade active (e.g., VIPRION/chassis-class hardware with multiple blades) - single-blade or standard appliance deployments are not stated to be affected and this is the primary limiting factor. Within that deployment, triggering is remote and unauthenticated (AV:N/PR:N/UI:N) via 'undisclosed' network traffic, so no credentials or user interaction are needed once the multi-blade precondition is met. Software versions that have reached End of Technical Support were not evaluated, so exposure cannot be assumed or ruled out for those builds. |
| Impact | This is a denial-of-service vulnerability (CWE-415 double free) that terminates the Traffic Management Microkernel (TMM), the data-plane core of F5 BIG-IP. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes low-complexity, remote, unauthenticated triggering with high availability impact only (VA:H) and no confidentiality or integrity impact (VC:N/VI:N) - consistent with a crash/DoS rather than data theft or code execution. Signals point toward moderate real-world priority rather than emergency: the CVSS 4.0 base score is 8.7 (high), but EPSS is only 0.35% (27th percentile), the CVE is NOT on CISA KEV, and no public exploit is referenced. These lower-urgency signals align with the narrow exploitation condition (the vulnerable code path only exists on multi-bladed chassis platforms with more than one blade), so the effective exposed population is a subset of all BIG-IP deployments. CONFLICTING SIGNAL: the input Tags label this 'Information Disclosure,' but the CVSS vector (VC:N, VI:N, VA:H), the CWE (double free), and the description (TMM termination) all indicate this is an availability/DoS issue, not disclosure - treat the 'Information Disclosure' label as incorrect. Net: a credible high-severity availability risk for organizations running multi-bladed F5 chassis, but not evidence of widespread or active exploitation at time of analysis. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends crafted or malformed network traffic to a BIG-IP system deployed on a multi-bladed chassis platform (more than one blade active). The traffic triggers a double-free condition in TMM, causing the microkernel to terminate and disrupting all traffic processing/failover on the affected device. No public exploit code is identified at time of analysis, and authentication requirements are unauthenticated per the PR:N vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Denial of service in F5 BIG-IP allows remote, unauthenticated attackers to terminate the Traffic Management Microkernel (TMM) and disrupt data-plane traffic processing. The flaw is a double-free (CWE-415) triggered by undisclosed network traffic, but exploitation is gated by a hardware precondition: the BIG-IP system must run on a multi-bladed chassis platform with more than one active blade, so single-blade and standard appliance deployments are not described as affected. No public exploit code has been identified at time of analysis, KEV status is not indicated, and EPSS is low at 0.35% (27th percentile); nevertheless, a TMM crash on a production load balancer can cause an immediate traffic outage. Vendor advisory: K000156912.
RemediationAI
No vendor-released patch was identified in the available input at time of analysis; consult F5 advisory K000156912 (https://my.f5.com/manage/s/article/K000156912) for the fixed-version matrix and any hotfix per branch, and plan upgrades off End-of-Technical-Support releases because the vendor explicitly did not evaluate them. Until a fix is applied, prioritize compensating controls that limit both the trigger and the blast radius: place BIG-IP virtual servers behind upstream network/volumetric DoS scrubbing or rate-limiting for untrusted traffic (trade-off: added latency and possible false positives on legitimate bursts), restrict internet exposure of services that do not need to be public (trade-off: application reachability changes), and monitor TMM restarts, blade health, and failover events so a crash is detected quickly. Verify that high-availability pairs and multi-blade chassis have working automatic failover, since a TMM termination on one blade or peer may shift load to the surviving unit; ensure the standby can absorb full production traffic (trade-off: failover capacity must be tested and provisioned). Because the flaw is described as affecting multi-blade platforms with more than one active blade, consolidating to a single-blade deployment would remove the stated precondition, but that is generally not operationally acceptable for capacity and redundancy reasons and should only be a temporary, risk-accepted measure. Apply the vendor's fixed release as soon as it is confirmed in K000156912.
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 Traffic Management Microkernel (TMM) is the data-plane process in F5 BIG-IP that handles packet processing, virtual-server traffic management, and many security and acceleration features, so its termination directly interrupts traffic handling rather than merely affecting the management plane. The root cause is CWE-415 (double free): a memory-management error in which the same allocation is released twice, which in TMM can corrupt internal state and cause the process to terminate. F5 describes the trigger only as 'undisclosed traffic,' so the precise packet sequence is not public; the independent assessment rates it AV:N/AC:L/PR:N/UI:N with an availability-only impact (C:N/I:N/A:H), consistent with remote, unauthenticated triggering once the deployment precondition is met. The CPE data lists the full BIG-IP module family (APM, AFM, AWAF, ASM, Analytics, AAM, AVR, Automation Toolchain, CGNAT, Container Ingress Services, DDoS Hybrid Defender, DNS, Edge Gateway, Fraud Protection Service, GTM, Link Controller, LTM, PEM, SSL Orchestrator, WebAccelerator, WebSafe, and BIG-IP Next variants), but the functional requirement for a multi-bladed chassis (for example, VIPRION-class hardware with more than one blade) is the dominant limiting factor. Versions that have reached End of Technical Support were not evaluated by the vendor, so exposure on EoTS builds is neither confirmed nor excluded.
Know when Big Ip Advanced Web Application Firewall 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
Remote unauthenticated network traffic (AV:N/PR:N/UI:N) with low complexity crashes TMM for a pure availability impact (A:H); no confidentiality or integrity effect.
Primary rating from Vendor (f5).
CVSS VectorVendor: f5
DescriptionCVE.org
When using a multi-bladed platform with more than one blade, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Executive ViewAI
F5 BIG-IP deployments on multi-blade chassis with more than one active blade face a remote denial-of-service condition that can terminate the Traffic Management Microkernel and interrupt data-plane traffic. Single-blade and standard appliance deployments are outside the described hardware precondition, and no public exploit has been identified at time of analysis, but an outage on a production load balancer could disrupt critical business services. Leadership should care because affected platforms may sit on important traffic paths and no vendor-released patch is currently identified.
No vendor-released patch identified at time of analysis; follow F5 advisory K000156912 for interim mitigations, inventory and monitor multi-blade BIG-IP chassis with more than one active blade, and prepare failover and outage response for affected data-plane traffic.
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
F5 BIG-IP APM (Access Policy Manager) contains a remote code execution vulnerability triggered by specific malicious tra
F5 BIG-IP contains an authenticated command injection in the iControl REST API and TMOS Shell (tmsh) save command. Authe
Undisclosed requests may bypass configuration utility authentication, allowing an attacker with network access to the BI
On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.
An authenticated SQL injection vulnerability exists in the BIG-IP Configuration utility which may allow an authenticated
BIG-IP monitor functionality may allow an attacker to bypass access control restrictions, regardless of the port lockdow
A directory traversal vulnerability exists in the BIG-IP Configuration Utility that may allow an authenticated attacker
On version 16.0.x before 16.0.1.2, 15.1.x before 15.1.3, 14.1.x before 14.1.4.1, 13.1.x before 13.1.4, 12.1.x before 12.
On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, 12.1.x
On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.
On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, 12.1.x
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB