External risk intelligence

BIG-IP TMM Denial of Service and Remote Code Execution Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-116953

The vulnerability affects F5 BIG-IP systems, which are typically deployed as internet-facing application delivery controllers, load balancers, or traffic gateways. Because the vulnerable component processes client traffic at the data plane on these devices, it is exposed to the public internet by design in common real-world deployments.

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

This advisory addresses a critical vulnerability in F5 BIG-IP systems that handle client traffic. If specific iRules are configured, undisclosed requests can cause a system component to terminate, leading to service disruption and potential remote code execution. This is a data plane issue, meaning it affects traffic processing directly.

  • Unauthenticated attackers can crash traffic systems.
  • It allows remote code execution, a severe threat.
  • Confirm relevance and exposure of affected systems.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending specially crafted requests to a BIG-IP system that has a specific iRule configured. These requests target the Traffic Management Microkernel (TMM) process, which handles client traffic. If the iRule uses the `GENERICMESSAGE::route` command, these requests can cause TMM to crash, leading to a denial-of-service. In some cases, this crash may also be leveraged for remote code execution.

  • Entry: Network-accessible BIG-IP with specific iRule.
  • Trigger: Specially crafted client traffic.
  • Risk: Denial-of-service and remote code execution.

Live Threat

Current exploitation, exposure, and threat context

When an iRule on a virtual server uses the GENERICMESSAGE::route command, undisclosed requests could cause the Traffic Management Microkernel (TMM) to terminate. This could lead to remote code execution and traffic disruption while the TMM process restarts.

  • System traffic and availability are at risk.
  • Malicious requests could trigger TMM termination.
  • Service disruption and potential remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

The BIG-IP platform team is likely responsible for addressing this critical vulnerability affecting the Traffic Management Microkernel (TMM). The immediate first step is to identify all BIG-IP systems, confirm their exposure and business criticality, and then coordinate with the appropriate application owners and vendor management to plan remediation, prioritizing systems that are internet-facing or handle sensitive traffic.

  • BIG-IP platform team ownership.
  • Verify internet-facing systems.
  • Plan vendor-coordinated remediation.

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 F5 BIG-IP software?

BIG-IP is an application delivery platform used to manage network traffic. It acts as a gateway or load balancer, sitting between the internet and backend servers to optimize performance, enhance security, and ensure application availability for enterprise services.

What does CVE-2026-116953 mean by stack-based buffer overflow?

The vulnerability involves CWE-121, a stack-based buffer overflow. This occurs when a program writes more data to a temporary memory area than it can hold. In this case, specific traffic can overwrite adjacent memory, causing the system process to crash or allowing unauthorized code execution.

How is this vulnerability triggered?

An attacker triggers this by sending specifically crafted network requests to a system. The vulnerability is only active if the device is running an iRule that uses the GENERICMESSAGE::route command. Standard traffic that does not utilize this specific command or virtual server configuration will not activate the bug.

Do I need to worry about this if my system is internal?

Halo Surface Signal indicates that BIG-IP systems are frequently deployed as internet-facing gateways, making them highly reachable. While the threat is primarily data-plane based, you should prioritize verifying any system accessible from outside your network perimeter, as these are most susceptible to remote, unauthenticated attempts.

When should I take action for this BIG-IP vulnerability?

You should act immediately by identifying all BIG-IP systems in your environment that process client traffic. Confirm whether any configured iRules utilize the GENERICMESSAGE::route command. Once identified, coordinate with your infrastructure teams to plan remediation, focusing on internet-facing devices first.

References