External risk intelligence

BIG-IP TMM Remote Code Execution via PEM Subscriber iRule

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-121805

The vulnerability affects BIG-IP systems configured with iRules that process client traffic at the data plane. BIG-IP devices are commonly deployed as internet-facing application delivery controllers, load balancers, and edge gateways, making them public-facing by design and inherently reachable from the internet 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 BIG-IP systems when specific iRules are used for client traffic processing. This issue can lead to system instability and potentially allow for remote code execution. While the control plane remains unaffected, the data plane disruption could impact traffic availability.

  • Undisclosed requests can crash the system.
  • A remote attacker could execute code.
  • Confirm relevance and exposure for critical systems.

Attack Path

How an attacker could exploit the issue

An attacker could target a BIG-IP system by sending specific network requests that are processed by an iRule containing the PEM::subscriber command. If this iRule is active on a virtual server, these requests could crash the Traffic Management Microkernel (TMM) process. This disruption could then potentially allow for remote code execution.

  • Network access required.
  • Undisclosed requests trigger vulnerability.
  • Denial-of-service and RCE risk.

Live Threat

Current exploitation, exposure, and threat context

When an iRule using PEM::subscriber is configured, an attacker could cause the Traffic Management Microkernel (TMM) to terminate. This could disrupt traffic and potentially lead to remote code execution.

  • System traffic disruption.
  • Undisclosed requests can trigger.
  • Potential for remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

For systems utilizing BIG-IP with iRules processing client traffic via PEM::subscriber, responsibility likely falls to infrastructure or platform teams managing the BIG-IP devices, in coordination with application owners if specific applications are impacted. The initial step is to locate all instances of the affected BIG-IP configuration, assess their external reachability and business criticality, identify the accountable system owner, and then prioritize remediation based on the potential risk.

  • Identify BIG-IP iRule configuration.
  • Verify external reachability and criticality.
  • Plan remediation with application owners.

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 BIG-IP and the TMM?

BIG-IP is a networking appliance used to manage application traffic, functioning as a load balancer or edge gateway. It relies on the Traffic Management Microkernel (TMM), a core engine that handles high-speed packet processing and traffic flow. The TMM operates in the data plane, meaning it directly manages the actual data moving between users and your applications.

What does CWE-121 mean for CVE-2026-121805?

CVE-2026-121805 is linked to CWE-121, which represents a stack-based buffer overflow. In plain terms, this means that specific, malformed network requests can push more data into a memory area than it can handle. This memory corruption causes the TMM process to crash, which is why an attacker can trigger a denial-of-service, or in some scenarios, leverage the overflow to run unauthorized code.

How is this vulnerability triggered?

An attacker triggers this flaw by sending specialized, undisclosed network requests to a BIG-IP system. Crucially, the vulnerability only exists if you have configured an iRule that uses the 'PEM::subscriber' command to process client traffic. If your virtual servers do not utilize this specific iRule command, the identified trigger path is not present.

Is my BIG-IP at risk?

According to Halo Surface Signal, this vulnerability is highly relevant because BIG-IP devices are frequently deployed as internet-facing gateways. Since the issue resides in the data plane, any system reachable from the internet that uses the vulnerable 'PEM::subscriber' iRule configuration is exposed to potential remote attacks without requiring authentication.

What should I do to address this CVE?

Start by auditing your BIG-IP configurations to identify any virtual servers currently using an iRule containing the 'PEM::subscriber' command. Once identified, evaluate the business criticality of those specific services and their exposure to the internet. Coordinate with your infrastructure and application teams to prioritize these systems for remediation according to your organization's internal change management processes.

References