F5 BIG-IP CVE-2025-58071
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach IPsec-configured BIG-IP over network
-
DeliverySend crafted IPsec traffic
-
ExploitTrigger uninitialized variable in TMM
-
ExecutionCrash Traffic Management Microkernel
-
ImpactDenial of service / traffic outage
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Variable initialization checks
|
| Exploitation Conditions | Exploitation requires that IPsec is configured on the BIG-IP system - this is the explicit precondition named in the description, and systems without IPsec configured are not exposed. When IPsec is configured, the attack is remote and unauthenticated against the traffic path (AV:N/PR:N/UI:N per CVSS 4.0), requiring no special privileges or user interaction. Additional limiting factors: software versions that have reached End of Technical Support (EoTS) were not evaluated, so exposure determination on such versions is unverified; impact is limited to availability (TMM termination / traffic disruption) with no data compromise. |
| Impact | This is a remote, unauthenticated denial-of-service affecting F5 BIG-IP, and the signals are internally consistent on that point: the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, no-privilege, no-interaction attack, while the impact metrics (VC:N/VI:N/VA:H) confirm the effect is purely availability loss - a TMM crash - with no confidentiality or integrity impact. The 8.7 score is therefore driven entirely by easy reachability plus a high-availability hit, not by data compromise. Priority should be moderated by real-world signals: EPSS is low at 0.37% (29th percentile), the CVE is NOT on CISA KEV, and no public exploit was identified, indicating no evidence of active or imminent widespread exploitation. The single most important risk reducer is configuration-dependence: the flaw is only reachable when IPsec is configured on the system, so environments not running IPsec are not exposed regardless of the network-facing CVSS vector. CONFLICT TO NOTE: the input 'Information Disclosure' tag contradicts the CVSS vector (VC:N - no confidentiality impact) and the CWE-457/TMM-termination description, which describe a crash/DoS, not disclosure - treat this as availability-only and verify against F5 advisory K000156746. |
| Exploit ScenarioDerived | An attacker with network reachability to an IPsec-configured BIG-IP sends undisclosed/crafted traffic that triggers use of an uninitialized variable (CWE-457) in the Traffic Management Microkernel, causing TMM to terminate and interrupting all traffic processing on the appliance. No authentication or user interaction is required (PR:N/UI:N), but the system must have IPsec enabled for the traffic path to be reachable. No public exploit code was 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
Denial of service in F5 BIG-IP allows remote, unauthenticated attackers to terminate the Traffic Management Microkernel (TMM) and disrupt traffic handling, but only on systems where IPsec is configured - deployments without an IPsec configuration are not exposed. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N with VC:N/VI:N/VA:H) and the corresponding CVSS 3.1 assessment agree that the effect is purely availability loss (a TMM crash), with no confidentiality or integrity impact, which makes this a high-severity (8.7) but non-compromising availability issue against appliances that are common internet-facing edge devices. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the EPSS score of roughly 0.37% (29th percentile) indicates low predicted exploitation likelihood in the near term, though the broad install base of BIG-IP keeps this worth prompt patching on IPsec-enabled systems.
RemediationAI
F5 addresses this through its standard BIG-IP release process and publishes the version-by-version fix matrix in advisory K000156746 (https://my.f5.com/manage/s/article/K000156746); that advisory is the authoritative source for the exact fixed build for each branch, and no specific fixed version number was included in the data supplied for this analysis, so confirm the target release against the advisory before upgrading - patch status is therefore best described as patch available per vendor advisory, with exact versions to be taken from the advisory. If an immediate upgrade is not possible, the most effective compensating control is scoping exposure: hosts that do not require IPsec should have the IPsec/IKE configuration removed entirely, which takes them out of the vulnerable code path at no functional cost. For hosts that must keep IPsec, restrict the reachable peer set as tightly as possible - constrain IKE and ESP traffic to known peer addresses via an upstream firewall or BIG-IP packet filter, and limit traffic selectors to the minimum required subnets - accepting that this narrows VPN connectivity and creates maintenance overhead whenever peers change. Operate BIG-IP in device groups with failover so a TMM termination triggers a peer takeover rather than a full outage, but note the same crafted traffic may crash the standby unit once it becomes active, so this is availability buffering rather than a fix. Supplement with alerting on TMM restart/abort events and on unexpected failover transitions, since the trigger traffic is undefined and signature-based detection is not reliable, and track any version still running an End-of-Technical-Support release as unverified exposure requiring an upgrade path.
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 user-space data-plane process in F5 BIG-IP that performs packet processing, virtual server load balancing, and - relevant here - IPsec/IKED traffic handling. The root cause class is CWE-457, Use of Uninitialized Variable: crafted, undisclosed network traffic delivered into the IPsec processing path causes TMM to operate on an uninitialized resource and abort, dropping all traffic being handled by that instance. The CPE list shows the defect lives in shared BIG-IP platform code rather than in a single module - the same TMM image is referenced across BIG-IP APM, AFM, Advanced WAF, Analytics, AAM, ASM, AVR, Automation Toolchain, CGNAT, Container Ingress Services, and the other licensed families enumerated in the advisory, and the tag set additionally names BIG-IP Next cloud-native network functions and BIG-IP Next for Kubernetes. Because the CVSS 4.0 vector omits the exploit-maturity (E) metric, it carries no vendor assertion of exploitation; notably, the supplied tag list includes an 'Information Disclosure' label that is not supported by either the CVE description or the authoritative vector, which explicitly scores confidentiality and integrity impact as None - the sole impact is availability. Versions that have reached End of Technical Support were excluded from F5's evaluation, so their exposure state is unverified rather than confirmed safe.
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, low-complexity, unauthenticated traffic crashes TMM, so AV:N/AC:L/PR:N/UI:N with availability-only impact (A:H, C:N/I:N); scope unchanged as the TMM crash stays within the component.
Primary rating from Vendor (f5).
CVSS VectorVendor: f5
DescriptionCVE.org
When IPsec is configured on the BIG-IP system, 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 appliances configured with IPsec face a high-severity availability risk: a remote, unauthenticated attacker could crash the Traffic Management Microkernel and interrupt traffic handling. Because BIG-IP is commonly deployed as an internet-facing edge device, leadership should prioritize identifying IPsec-enabled instances, reducing exposure, and planning for a vendor patch once released; no public exploit identified at time of analysis.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling or removing IPsec configuration on BIG-IP appliances where it is not operationally required, restricting network access to IPsec-enabled interfaces, monitoring for TMM restarts and traffic-handling disruptions, validating HA/failover, and monitoring F5 guidance for workarounds.
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