Skip to content
Security Alerts

CVE-2026-120292 and 3 More: TMM Crash and Possible RCE in F5 BIG-IP

F5 disclosed four stack-based buffer overflows in the BIG-IP Traffic Management Microkernel. With specific iRules or APM policies, an unauthenticated attacker can disrupt traffic and potentially execute code...

Summary

ParameterValue
CVE ID (lead entry)CVE-2026-120292
Vulnerabilities covered4 critical (CVE-2026-120292, CVE-2026-120722, CVE-2026-121805, CVE-2026-123637)
Alert SourceGitHub Advisory - Critical Vulnerability
CVE Publication Year2026
Date Published2026-11-18
VendorF5
ProductBIG-IP (Traffic Management Microkernel, including the APM module)
Vulnerability Typestack-based buffer overflow (CWE-121) → denial of service, possible remote code execution
CVSS Score9.8 (critical; CVSS 4.0: 9.3)
EPSS ScoreNo data
CISA KEVNo
RansomwareNot confirmed

Vulnerability Description

Source: NVD (CNA: F5), F5 K articles

On 18 November 2026 F5 published four vulnerabilities in the BIG-IP Traffic Management Microkernel (TMM) — the process that handles application traffic on virtual servers. In each case, undisclosed crafted requests cause TMM to terminate and may lead to remote code execution (RCE). The attacker does not need to be authenticated.

CVEVulnerable conditionF5 article
CVE-2026-120292HTTP profile and an iRule using the MR::message route command on a virtual serverK000163940
CVE-2026-120722iRule processing client traffic with the DNS::scrape commandK000163945
CVE-2026-121805iRule processing client traffic with the PEM::subscriber commandK000163946
CVE-2026-123637BIG-IP APM provisioned and a per-request policy with the Client Information and Endpoint Security agentsK000163937

Traffic through the device is disrupted while TMM restarts. F5 states that these are data plane issues only — the control plane (management interface) is not exposed. Versions that have reached End of Technical Support (EoTS) were not evaluated. The vendor does not report exploitation in the wild; the flaws are not in the CISA KEV catalog.

Required Actions

  1. Check whether your devices match the conditions in the table: iRules using MR::message route, DNS::scrape or PEM::subscriber, or APM per-request policies with the Client Information and Endpoint Security agents.
  2. Install the fixed versions listed in articles K000163940, K000163945, K000163946 and K000163937 for your BIG-IP branch.
  3. Until you update, check the K articles for workarounds applicable to your configuration and assess their impact on applications before applying them.
  4. Move devices running EoTS versions to a supported branch — F5 does not evaluate them and will not fix them.
  5. Monitor unexpected TMM restarts and failover events in HA clusters — they may indicate exploitation attempts.

Who Is Affected?

Organizations using F5 BIG-IP (LTM and other modules that use iRules and, for CVE-2026-123637, BIG-IP APM) as a load balancer, application gateway or VPN gateway. Virtual servers with the described configuration are exposed; their traffic usually comes from the internet, so the flaws can be exploited externally.

Sources


Need help securing your systems? nFlo team offers vulnerability management and 24/7 SOC services. Contact us.

Learn More

Share:

Talk to an expert

Have questions about this topic? Get in touch with our specialist.

Sales Representative
Grzegorz Gnych

Grzegorz Gnych

Sales Representative

Response within 24 hours
Expert consultation
Individual approach

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations