External risk intelligence

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

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-120285

The vulnerability affects BIG-IP systems, which are typically deployed as internet-facing application delivery controllers, load balancers, and gateways. These devices are designed to receive and process traffic directly from the public internet, making the data plane interface susceptible to unauthenticated remote requests in standard configurations.

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 the BIG-IP system that could allow an unauthenticated remote attacker to disrupt traffic by causing the system's Traffic Management Microkernel to terminate. This issue may also present an opportunity for remote code execution.

  • Disruption of traffic via system termination.
  • Impacts internet-facing application delivery.
  • Assess exposure and confirm relevance.

Attack Path

How an attacker could exploit the issue

An attacker can target this vulnerability by sending specially crafted requests to a BIG-IP system. If the system is configured with an HTTP profile and an iRule that uses the `PSC::ip_address` command, these requests can cause a critical component called TMM to crash. This crash disrupts traffic and could potentially allow the attacker to gain remote code execution.

  • Entry: Unauthenticated network requests.
  • Trigger: HTTP profile with specific iRule.
  • Risk: Denial-of-service and remote code execution.

Live Threat

Current exploitation, exposure, and threat context

When an HTTP profile and an iRule containing the PSC::ip_address command are configured, undisclosed requests could cause the Traffic Management Microkernel (TMM) to terminate, potentially leading to remote code execution. This vulnerability is a data plane issue only and does not expose the control plane.

  • System process could terminate.
  • Unauthenticated requests could trigger termination.
  • Denial-of-service and potential code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability affects the data plane of BIG-IP systems and requires immediate attention from teams managing network infrastructure and application delivery. The first practical step is to identify all instances of the affected BIG-IP technology, confirm their exposure and business criticality, and then assign ownership for remediation. This includes coordinating with the vendor for guidance and planning maintenance windows to minimize service disruption.

  • Infrastructure and Network Security teams own the issue.
  • Verify BIG-IP system reachability and criticality.
  • Coordinate vendor fix deployment and plan maintenance.

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?

BIG-IP is a networking platform from F5 that acts as an application delivery controller. It manages, secures, and optimizes incoming web traffic by balancing loads between servers, acting as a gateway that sits in front of applications to ensure they remain available and perform well for users.

What is the weakness behind CVE-2026-120285?

This vulnerability is classified as CWE-121, or a stack-based buffer overflow. In plain terms, this means the software does not correctly handle the amount of data being processed in a specific memory area. Because of this, sending specific, malformed data can overwhelm the system's memory, causing the Traffic Management Microkernel to crash or potentially allowing an attacker to run their own code.

How can an attacker trigger this vulnerability?

An attacker needs to send specific, crafted HTTP requests to a system configured with both an HTTP profile and an iRule that uses the 'PSC::ip_address' command. It is important to note that this is exclusively a data plane issue; requests that do not involve this specific combination of configuration and traffic command do not trigger the flaw.

Is my BIG-IP system at high risk according to Halo Surface Signal?

Yes. Halo Surface Signal classifies this as highly relevant because BIG-IP systems are typically deployed as internet-facing gateways. Because these devices are specifically designed to accept and process traffic directly from the public internet, they are frequently exposed to the unauthenticated network requests required to trigger this vulnerability.

What are the first steps to take?

Begin by auditing your environment to locate all BIG-IP instances that utilize both an HTTP profile and the 'PSC::ip_address' command in their iRules. Once identified, prioritize these devices based on their business criticality and internet reachability. Coordinate with your team to review official vendor documentation and prepare maintenance windows for applying updates.

References