External risk intelligence

F5 BIG-IP DNS Scrape TMM Crash and Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-120722

The vulnerability affects F5 BIG-IP systems, which are typically deployed as internet-facing application delivery controllers, load balancers, or gateway appliances. The issue occurs within the data plane during the processing of client traffic via iRules, placing it directly in the path of public-facing network traffic handled by the device.

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 exists in F5 BIG-IP systems when specific traffic processing rules are enabled. This issue can disrupt traffic and potentially allow attackers to execute code remotely, impacting the availability of services managed by these systems. The main concern is confirming relevance and exposure to understand the potential impact on our environment.

  • Client traffic rules can crash system.
  • Remote attackers may gain code execution.
  • Confirm if our systems are impacted.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted network requests to a BIG-IP system configured with a specific iRule. These requests would target the Traffic Management Microkernel (TMM) via the DNS::scrape command, potentially causing it to crash and leading to remote code execution.

  • No authentication or user interaction needed.
  • Crafted requests trigger TMM crash.
  • Leads to denial-of-service and RCE.

Live Threat

Current exploitation, exposure, and threat context

When an iRule on a BIG-IP virtual server uses the DNS::scrape command, specific requests could cause the Traffic Management Microkernel (TMM) to terminate, potentially allowing remote code execution and disrupting traffic.

  • System processes could terminate unexpectedly.
  • Undisclosed requests may trigger TMM failure.
  • Remote code execution is a potential outcome.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts F5 BIG-IP systems when specific iRules are configured, potentially leading to DoS and RCE. The first practical step is for infrastructure and security teams to identify all BIG-IP systems, confirm the presence of the vulnerable iRule configuration, and assess their exposure to external traffic. Once identified, the accountable owner should be confirmed, and a risk-based remediation plan, considering maintenance windows and vendor coordination, should be developed.

  • Infrastructure and Security teams own the issue.
  • Verify BIG-IP systems with vulnerable iRules.
  • Plan remediation based on confirmed exposure.

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 and why is it used?

F5 BIG-IP is a hardware and software platform that acts as a gatekeeper for applications. It functions as a load balancer and application delivery controller, managing incoming network traffic to ensure that services remain fast and available. By sitting between the internet and backend servers, it helps distribute work efficiently and provides security, making it a critical component in complex network infrastructures.

What kind of vulnerability is CVE-2026-120722?

This vulnerability is classified as a stack-based buffer overflow, identified by CWE-121. In simple terms, the system tries to store more data in a specific area of memory than it is designed to hold. In this case, the `DNS::scrape` command fails to handle certain malformed data correctly, overwriting adjacent memory. This memory corruption is what allows the system to crash or potentially run unauthorized commands.

How does an attacker trigger this vulnerability?

An attacker triggers this by sending specially crafted network packets to a BIG-IP system. This only happens if a virtual server is currently configured with an iRule using the `DNS::scrape` command. If that command is not present in your iRule configurations, these specific malicious requests cannot trigger this particular memory corruption issue.

Is my BIG-IP system at risk?

Halo Surface Signal indicates that BIG-IP systems are often deployed as internet-facing gateways, placing them directly in the path of public traffic. Since this flaw exists in the data plane—the part of the device that processes live traffic—it is reachable from the internet without requiring authentication. If your device handles public DNS or traffic requests using the affected iRule, it is accessible to remote attackers.

What should I do if I run this technology?

First, perform an inventory to locate all BIG-IP systems in your environment. Next, audit your active iRules to check for the use of the `DNS::scrape` command. If you find this configuration, prioritize it for review with your infrastructure team. Work to verify the exposure level of these systems, identify who manages them, and plan for updates according to vendor guidance and your standard maintenance schedules.

References