F5 BIG-IP CVE-2025-61951
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach DTLS 1.2 virtual server
-
DeliverySend crafted DTLS 1.2 traffic
-
ExploitTrigger out-of-bounds read in TMM
-
ExecutionCrash TMM process
-
ImpactData-plane outage / dropped traffic
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a very specific, non-default configuration: a DTLS 1.2 virtual server must be enabled with a Server SSL profile that has a certificate and key configured and the SSL Sign Hash set to ANY, AND the backend server must be configured for DTLS 1.2 with client authentication. Devices without a DTLS 1.2 virtual server, or with a different SSL Sign Hash setting, or without backend client authentication, are not affected. Additionally, software versions past End of Technical Support (EoTS) were not evaluated and are out of scope. No authentication is required against a vulnerable configuration (PR:N), and no user interaction is needed (UI:N); the primary limiting factor is the narrow configuration prerequisite rather than access control. |
| Impact | This is a denial-of-service vulnerability in F5 BIG-IP's Traffic Management Microkernel (TMM), the core data-plane process whose termination disrupts all traffic handling on the device. The input CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N, VC:N/VI:N/VA:H) frames it as a network-reachable, unauthenticated availability-only impact - no confidentiality or integrity loss - which is consistent with the description of TMM terminating on undisclosed traffic. However, the real-world risk is substantially gated by configuration: exploitation only applies when a DTLS 1.2 virtual server is paired with a specific Server SSL profile (certificate, key, SSL Sign Hash set to ANY) and a backend configured for DTLS 1.2 with client authentication. This is a non-default, relatively uncommon deployment, so the vendor's AC:L arguably understates the practical attack complexity. The signals otherwise point to low urgency: EPSS is only 0.24% (14th percentile), the CVE is NOT in CISA KEV, and no public exploit code has been identified. There is no evidence of active exploitation. Net assessment: a genuine high-severity DoS for the narrow set of organizations running the exact affected DTLS configuration, but a low-priority, config-dependent issue for the broader BIG-IP fleet. Note one data inconsistency: the input Tags list 'Information Disclosure', yet CVSS VC:N and the description (TMM termination) indicate a pure availability impact, not disclosure - the tag appears mislabeled. |
| Exploit ScenarioDerived | An attacker who can reach a BIG-IP virtual server configured for DTLS 1.2 (with the specific Server SSL profile and backend client-authentication setup described) sends specially crafted DTLS traffic. The malformed traffic triggers an out-of-bounds read (CWE-125) that terminates the TMM process, dropping all traffic processed by the device until it restarts. No public exploit code is known, and the network attack vector (AV:N/PR:N) means no authentication is required against a vulnerable configuration. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Undisclosed network traffic can crash the Traffic Management Microkernel (TMM) on F5 BIG-IP, the data-plane process responsible for handling all traffic on the device, resulting in a denial of service against the whole system. Exploitation requires a narrow, non-default configuration: a DTLS 1.2 virtual server with a Server SSL profile that has a certificate and key installed and the SSL Sign Hash set to ANY, plus a backend server enabled for DTLS 1.2 with client authentication; no authentication or user interaction is required against a device in that state, but other configurations are not affected. No public exploit code has been identified at time of analysis and CISA KEV does not list this issue; EPSS is low at 0.24% (14th percentile), consistent with an availability-only flaw gated by a specific configuration rather than a broadly weaponizable one.
RemediationAI
F5 has published an advisory at https://my.f5.com/manage/s/article/K000151309 covering this issue; consult it for the specific patched BIG-IP releases applicable to your branch, since no exact fix version is included in the supplied data. Because exploitation depends entirely on configuration, effective interim mitigations are straightforward and can be applied before upgrading: remove the DTLS 1.2 virtual server if it is not required, or change the Server SSL profile's SSL Sign Hash setting away from ANY (for example, to a specific hash such as SHA-256) so the vulnerable code path is not reached - this is the most surgical fix but may break clients that depend on ANY-negotiated signatures. Alternatively, disable client authentication on the DTLS 1.2 backend server, or downgrade/disable DTLS 1.2 on the virtual server, though each of these degrades the security posture or functionality of the affected service and should be weighed against the denial-of-service risk. Deployments with no DTLS 1.2 virtual server, or with a different SSL Sign Hash value, or without backend client authentication are not vulnerable and need no change. Note that upgrading is required in the long term, and versions past End of Technical Support are out of scope and must be moved to a supported release.
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 flaw is a CWE-125 out-of-bounds read occurring in the F5 Traffic Management Microkernel (TMM), the user-space data-plane component that processes and forwards traffic for all BIG-IP modules. The crash path is triggered by DTLS 1.2 traffic traversing a virtual server configured with a Server SSL profile that has a certificate and key and the SSL Sign Hash option set to ANY, with a backend server also configured for DTLS 1.2 and client authentication. Under that combination, malformed or unexpected datagrams cause TMM to read beyond the boundaries of an allocated buffer, which terminates the process rather than yielding data - the observable outcome is availability loss, not information disclosure, despite the surrounding product tags. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L, 8.7) and the independent CVSS 3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) agree on remote, unauthenticated availability impact; the 3.1 rating scores the attack as high complexity, reflecting the tight configuration prerequisite rather than any authentication barrier. Affected CPE entries span the entire BIG-IP module family - Access Policy Manager, Advanced Firewall Manager, Advanced WAF, Analytics, Application Acceleration Manager, Application Security Manager, Application Visibility and Reporting, Automation Toolchain, Carrier-Grade NAT, Container Ingress Services, and related modules - because they all sit on the same TMM data plane. Software versions past End of Technical Support were explicitly not evaluated.
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:L
Network-reachable and unauthenticated (AV:N/PR:N), but the required non-default DTLS/SSL configuration raises complexity (AC:H); impact is TMM crash only, so C:N/I:N/A:H.
Primary rating from Vendor (f5).
CVSS VectorVendor: f5
DescriptionCVE.org
Undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate. This issue may occur when a Datagram Transport Layer Security (DTLS) 1.2 virtual server is enabled with a Server SSL profile that is configured with a certificate, key, and the SSL Sign Hash set to ANY, and the backend server is enabled with DTLS 1.2 and client authentication. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Executive ViewAI
F5 BIG-IP devices configured with a specific, non-default DTLS 1.2 setup are vulnerable to a denial-of-service attack that can crash the Traffic Management Microkernel (TMM), halting all traffic processing and potentially causing widespread service outages. Organizations relying on BIG-IP for critical application delivery or security services should assess their exposure and implement interim mitigations, as no patch is currently available. Leadership should prioritize this due to the high severity and potential for significant operational disruption.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling DTLS 1.2 on affected virtual servers, removing the Server SSL profile or changing SSL Sign Hash from ANY, disabling client authentication for DTLS 1.2 backend servers, and restricting network access to affected virtual servers. Monitor F5 advisory for updates.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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