External risk intelligence

BIG-IP TMM DoS and RCE Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-120292

The vulnerability affects BIG-IP virtual servers configured with HTTP profiles and iRules. BIG-IP systems are commonly deployed as internet-facing application delivery controllers, gateways, or load balancers, making the data plane directly reachable to traffic from the public internet in standard deployment patterns.

Remote Code Execution

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in a specific configuration of BIG-IP virtual servers, where undisclosed requests can cause a system process to terminate, potentially leading to disruption and unauthorized code execution. This issue is a data plane concern, meaning it directly impacts traffic handling rather than administrative access.

  • System process termination impacts traffic delivery.
  • Allows remote attackers to disrupt services.
  • Confirm relevance and exposure to this configuration.

Attack Path

How an attacker could exploit the issue

An attacker can reach the vulnerable component by sending specific, undisclosed requests over the network to a BIG-IP system. This is possible when the system is configured with an HTTP profile and an iRule that uses the MR::message route command. Successful exploitation can cause a denial-of-service and potentially lead to remote code execution.

  • Network access required for attack.
  • Special HTTP requests trigger vulnerability.
  • System crash, potential code execution.

Live Threat

Current exploitation, exposure, and threat context

When an HTTP profile and an iRule using the MR::message route command are configured, certain requests could cause the Traffic Management Microkernel (TMM) to terminate. This vulnerability is a data plane issue only and does not expose the control plane.

  • System traffic disruption is possible.
  • Undisclosed requests may trigger TMM termination.
  • Remote code execution is a potential outcome.

Operational Fix

Recommended remediation, mitigation, and detection steps

The BIG-IP platform team or the infrastructure team responsible for network traffic management is likely to own this vulnerability. The first practical step is to identify all BIG-IP virtual servers with HTTP profiles and iRules using the MR::message route command, then determine their business criticality and external reachability. Planning remediation should be based on this risk assessment, which may involve coordination with the vendor if a fix is available and requires specific deployment.

  • Identify BIG-IP instances with HTTP profiles and iRules.
  • Confirm external reachability and business criticality.
  • Plan risk-based remediation and vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the BIG-IP system affected by CVE-2026-120292?

BIG-IP is a networking platform from F5 that functions as an application delivery controller. It acts as a gatekeeper for web traffic, performing tasks like load balancing and traffic management to ensure applications remain available and performant. The Traffic Management Microkernel (TMM) is the high-performance core engine within the system responsible for processing and routing the actual data packets moving through the network.

What is the weakness class behind this CVE?

This vulnerability is classified as CWE-121, which refers to stack-based buffer overflow. In plain terms, the software fails to properly manage the memory allocated for incoming data requests. When the system receives specific, malformed traffic, it can overwrite adjacent memory areas, leading to instability or the ability for an attacker to execute their own code.

How can an attacker trigger this vulnerability?

An attacker needs to send specific, crafted network requests to a BIG-IP system that has a very precise configuration: an active HTTP profile paired with an iRule that utilizes the 'MR::message route' command. If these specific components are not simultaneously configured and active on a virtual server, the traffic will not reach the vulnerable code path.

Is my BIG-IP system at risk if it is not internet-facing?

Halo Surface Signal indicates that BIG-IP systems are commonly deployed as gateways or load balancers exposed to the public internet, which makes them highly reachable for this data plane attack. While the risk is highest for internet-facing instances, any system reachable by a potential attacker on your network—even internally—should be evaluated against this vulnerability.

What should I do first to manage this risk?

Begin by auditing your BIG-IP virtual servers to identify which ones use both an HTTP profile and an iRule containing the 'MR::message route' command. Once you have a list of these specific instances, prioritize them based on their business criticality and network exposure, then coordinate with your infrastructure team to review vendor guidance for mitigation or patching.

References