Cyber & AI intelligence
Briefs indexed3924
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-120292 2026-11-19

F5 BIG-IP TMM Flaw in MR::message route iRule Command Allows Unauthenticated DoS and Possible RCE (CVE-2026-120292)

"CVE-2026-120292 is a critical (CVSS 3.1: 9.8) data-plane vulnerability in F5 BIG-IP and BIG-IP Next for Kubernetes: undisclosed requests can terminate the Traffic Management Microkernel (TMM) and may lead to remote code…"

CVE-2026-120292 is a critical (CVSS 3.1: 9.8) data-plane vulnerability in F5 BIG-IP and BIG-IP Next for Kubernetes: undisclosed requests can terminate the Traffic Management Microkernel (TMM) and may lead to remote code execution.

What Is It

The flaw affects virtual servers configured with both an HTTP profile and an iRule that uses the MR::message route command. On those virtual servers, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate, and this may lead to remote code execution (RCE). The weakness is classified as CWE-121 (stack-based buffer overflow).

F5 published the CVE on 2026-11-18. NVD lists its status as "Received", which means NVD has not yet completed its own analysis.

Why It Matters

The CISA KEV entry supplied for this CVE is empty. This brief has no KEV confirmation of active exploitation and no KEV-mandated required action or due date.

What's Vulnerable

You are only exposed if a virtual server has both an HTTP profile and an iRule using MR::message route. The affected branches and the builds listed as unaffected are:

F5 BIG-IP - 21.1.0 branch: fixed in BIGIP-21.1.0.4.0.19.3-ENG - 17.5.0 branch: fixed in BIGIP-17.5.1.11.0.61.12-ENG and BIGIP-17.5.1.10.0.80.35-ENG - 17.1.0 branch: fixed in BIGIP-17.1.3.7.0.21.4-ENG and BIGIP-17.1.3.6.0.14.20-ENG

F5 BIG-IP Next for Kubernetes - 2.4.0 branch: fixed in BNK-2.4.2-EHF1 - 2.3.0 branch: fixed in BNK-2.3.4-EHF1 - 2.2.0 branch: fixed in BNK-2.2.5-EHF1

F5 notes that it did not evaluate software versions that have reached End of Technical Support (EoTS).

Patch Status

F5 lists fixed builds for every affected branch, as shown above. Administrators should:

  1. Check whether any virtual servers combine an HTTP profile with an iRule that calls MR::message route.
  2. Move affected systems to the unaffected build for their branch.
  3. Check F5 advisory K000163940 for vendor guidance.

No CISA-mandated remediation deadline applies, because the supplied KEV data has no entry for this CVE.

Sources