External risk intelligence

BIG-IP APM Denial of Service and Remote Code Execution Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-123637

The vulnerability exists in BIG-IP APM (Access Policy Manager), which is a gateway solution designed to be public-facing to manage remote access, authentication, and policy enforcement for internet traffic. Because it acts as an edge service and is intended to process unauthenticated or pre-authentication requests at the network perimeter, public internet exposure is a core deployment pattern.

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 concerns a critical vulnerability in BIG-IP APM, a technology used for managing access and security policies for network traffic. The issue could allow unauthorized remote attackers to disrupt services or potentially execute code on affected systems. The primary concern is confirming if this specific technology is in use and if it is exposed to potential threats.

  • A critical flaw allows remote code execution.
  • It impacts network access management systems.
  • Confirm relevance and exposure immediately.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending specific, undisclosed requests to a BIG-IP system that has APM provisioned and configured with a per-request policy. This policy must include both the Client Information and Endpoint Security agents. The vulnerability lies within the Traffic Management Microkernel (TMM) and, when triggered, can lead to TMM termination and potentially remote code execution.

  • Unauthenticated network requests.
  • Triggered by specific APM policy requests.
  • Denial-of-service, potential RCE.

Live Threat

Current exploitation, exposure, and threat context

When BIG-IP APM is configured with specific policies, undisclosed requests could cause the Traffic Management Microkernel (TMM) to terminate. This may lead to a denial-of-service condition and potentially remote code execution, affecting the availability and integrity of the BIG-IP system's data plane.

  • System availability and integrity.
  • Undisclosed requests could trigger TMM termination.
  • Denial-of-service and potential remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in BIG-IP APM, impacting the Traffic Management Microkernel (TMM), requires immediate attention from F5 BIG-IP administrators and the security operations team responsible for network edge devices. The first practical step involves identifying all BIG-IP APM instances, confirming their exposure to the internet or untrusted networks, and assessing the business criticality of affected virtual servers. Once identified and prioritized, a coordinated plan with the infrastructure or platform team should be established to address the issue, considering potential vendor coordination and maintenance windows.

  • Infrastructure/Platform team owns remediation.
  • Verify external reachability and asset criticality.
  • Plan and execute vendor-recommended fix.

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

BIG-IP APM is an access policy management module for F5 BIG-IP systems. It functions as a gateway that controls network traffic by enforcing authentication and security policies. Organizations typically deploy it at the network edge to manage remote access for users and protect applications, acting as a broker between the public internet and internal corporate resources.

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

CWE-121 refers to a stack-based buffer overflow, a memory safety weakness. In the context of CVE-2026-123637, this means that providing specially crafted, undisclosed input can overwrite memory areas used by the Traffic Management Microkernel. This unexpected memory access can cause the system process to crash, leading to service disruption, or potentially allow an attacker to run their own code on the device.

What triggers the vulnerability in BIG-IP APM?

The vulnerability is triggered when a BIG-IP system has APM provisioned and a specific virtual server is configured with a per-request policy containing both Client Information and Endpoint Security agents. If these agents are not present in the active policy, the specific path leading to this memory corruption is not invoked by incoming requests.

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

Halo Surface Signal identifies BIG-IP APM as a technology inherently designed to face the internet to manage remote access. While the flaw is a data plane issue—meaning it does not expose the device's control plane—it remains reachable to any sender who can communicate with the configured virtual server. If your instance is not exposed to the public internet, you are only at risk from attackers already positioned within your internal network who can reach that specific service.

How do I respond to this threat?

Start by identifying all BIG-IP instances running the APM module. Review your virtual server configurations to see if they utilize both the Client Information and Endpoint Security agents in their policies. Prioritize these systems based on their reachability and the criticality of the services they protect. Finally, coordinate with your infrastructure team to apply the vendor-provided remediation, such as a software update, during a planned maintenance window.

References