Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessNetwork access to UDP virtual server
-
DeliverySend crafted UDP payload
-
ExploitTrigger stack overflow in TMM classification engine
-
ExecutionTMM process termination
-
ImpactService denial
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | UDP virtual server with classification profile enabled on F5 BIG-IP, BIG-IP Next CNF, or BIG-IP Next for Kubernetes. Classification profiles are advanced traffic analysis features not enabled by default on all virtual servers, requiring deliberate administrator configuration for application identification and policy enforcement. Exploitation requires network access to the UDP virtual server's listening address and port. Standard UDP virtual server deployments without classification profiles are not vulnerable. The specific request patterns that trigger the overflow are undisclosed by F5, limiting attacker knowledge but also defender testing capabilities. |
| Impact | The CVSS 7.5 (High) rating reflects maximum network exploitability (AV:N/AC:L/PR:N/UI:N) with complete availability impact (A:H). However, real-world risk is constrained by specific deployment requirements: exploitation only affects UDP virtual servers with classification profiles enabled, which is not a universal default configuration. The network-accessible attack vector and low complexity are concerning for internet-facing UDP services (DNS, SIP, RADIUS), but the attack surface is limited to organizations using F5's advanced traffic classification features on UDP protocols. No KEV listing or public exploit code identified, suggesting exploitation has not been observed in the wild. The stack overflow vulnerability class (CWE-121) is well-understood by attackers but typically requires protocol-specific expertise to weaponize. Priority should be elevated for organizations running UDP-based services with classification profiles on internet-facing BIG-IP systems, particularly DNS infrastructure and VoIP gateways. Organizations not using classification profiles on UDP virtual servers face minimal practical risk despite the high CVSS score. |
| Exploit ScenarioDerived | An unauthenticated remote attacker identifies a BIG-IP virtual server configured to handle UDP traffic with a classification profile enabled, such as a DNS load balancer or SIP gateway. The attacker crafts malicious UDP packets containing payload patterns that trigger the stack buffer overflow in TMM's classification engine, causing immediate TMM process termination and resulting in denial of service for all traffic processed by that TMM instance, disrupting critical services for legitimate users. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 13, 2026
Remote denial-of-service in F5 BIG-IP allows unauthenticated attackers to crash the Traffic Management Microkernel (TMM) by sending specially crafted UDP requests to virtual servers with classification profiles enabled. The vulnerability affects BIG-IP, BIG-IP Next CNF, and BIG-IP Next for Kubernetes platforms. No public exploit identified at time of analysis, with EPSS data unavailable for this recent CVE. Vendor-released patch available per F5 advisory K000158038.
RemediationAI
Apply vendor-released patches per F5 Security Advisory K000158038 (https://my.f5.com/manage/s/article/K000158038), which provides specific fixed versions for each affected product line. Patching is the primary remediation and should be prioritized for internet-facing UDP virtual servers with classification profiles. As a temporary mitigation for systems that cannot be immediately patched, administrators can disable classification profiles on UDP virtual servers, though this removes traffic analysis capabilities and may impact application visibility and policy enforcement. Alternatively, restrict UDP virtual server access to trusted networks using firewall rules or BIG-IP AFM policies, trading off service availability for security. For critical UDP services like DNS or SIP, consider moving to non-affected load balancers temporarily or implementing redundant BIG-IP instances with staggered patching schedules to maintain availability during remediation. Review F5 advisory for product-specific upgrade paths and compatibility considerations before applying patches to production systems.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
F5 BIG-IP's Traffic Management Microkernel (TMM) is the core data plane component responsible for processing and forwarding network traffic through virtual servers. This vulnerability stems from a stack-based buffer overflow (CWE-121) in TMM's handling of UDP traffic when classification profiles are applied. Classification profiles analyze traffic patterns for application identification and policy enforcement. The flaw occurs during parsing or processing of undisclosed UDP request patterns, causing a write operation to exceed stack boundaries and triggering TMM process termination. Affected products span the traditional BIG-IP appliances (cpe:2.3:a:f5:big-ip), container-native BIG-IP Next CNF (Cloud-Native Function), and BIG-IP Next for Kubernetes deployments, indicating the vulnerable code exists across multiple F5 product architectures.
Know when Big Ip Next 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
Primary rating from Vendor (f5) · only source for this CVE.
CVSS VectorVendor: f5
Lifecycle Timeline
2DescriptionCVE.org
When a classification profile is configured on a UDP virtual server, undisclosed requests 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 platforms are vulnerable to unauthenticated remote denial-of-service attacks that can crash the Traffic Management Microkernel, disrupting load balancing and application availability across affected infrastructure. Organizations running BIG-IP, BIG-IP Next CNF, or BIG-IP Next for Kubernetes with classification profiles enabled require immediate patching to prevent service interruptions.
If immediate patching is not feasible: (1) Restrict UDP traffic to virtual servers with classification profiles enabled using network ACLs or firewall rules; (2) Implement rate limiting on UDP requests to affected virtual servers; (3) Disable classification profiles if not operationally critical; (4) Monitor TMM process health and implement automated restart policies. Apply vendor patch as the primary remediation.
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.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
More in Big Ip Next For Kubernetes
View allUncontrolled memory consumption in F5 BIG-IP Next for Kubernetes, BIG-IP Next Cloud-Native Network Functions and BIG-IP
Denial of service in F5 BIG-IP allows remote, unauthenticated attackers to terminate the Traffic Management Microkernel
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
A remote, unauthenticated denial-of-service condition exists in F5 BIG-IP Policy Enforcement Manager (and the BIG-IP Nex
Memory-exhaustion denial of service in F5 BIG-IP affects any virtual server configured with an HTTP/2 profile, where a r
Remote unauthenticated attackers can crash F5 BIG-IP and BIG-IP Next Traffic Management Microkernel (TMM) processes via
Traffic Management Microkernel (TMM) crashes in F5 BIG-IP Virtual Edition and hardware platforms when SSL profiles are c
Denial of service in F5 BIG-IP virtual servers with SSL profiles allows remote unauthenticated attackers to exhaust conn
Repeated calls to an undisclosed API endpoint can force the Traffic Management Microkernel (TMM) to terminate on F5 BIG-
Memory exhaustion in F5 BIG-IP Next can be induced when iRules configured through the declarative API are repeatedly re-
An HTTP/2 implementation flaw allows a denial-of-service (DoS) that uses malformed HTTP/2 control frames in order to bre
EUVD-2026-29990
GHSA-7vhg-fvrv-7x3q
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB