Automated Threat Modeling

Brief Summary: F5 BIG-IP CVE-2026-120292, a Stack-Based Buffer Overflow in TMM Reached via the MR::message route iRules Command

A brief summary of CVE-2026-120292, a critical stack-based buffer overflow in F5 BIG-IP TMM that is reachable when a virtual server combines an HTTP profile with an iRule using MR::message route. The post covers the conditional attack surface, affected versions, and F5's engineering hotfix guidance.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-18

Brief Summary: F5 BIG-IP CVE-2026-120292, a Stack-Based Buffer Overflow in TMM Reached via the MR::message route iRules Command

Introduction

F5 has disclosed a critical flaw in the BIG-IP Traffic Management Microkernel (TMM) that lets a remote, unauthenticated attacker crash the data plane, and possibly execute code, on systems where a virtual server pairs an HTTP profile with an iRule that calls MR::message route. TMM is the process that carries application traffic through BIG-IP, so each crash interrupts service for the applications behind the affected virtual server until TMM restarts.

F5 rates CVE-2026-120292 Critical, with a CVSS v3.1 score of 9.8 and a CVSS v4.0 score of 9.3, and classifies it as CWE-121 (stack-based buffer overflow). It was published on November 18, 2026, as part of an out-of-band security notification (K000164058) covering several related BIG-IP iRule flaws. For defenders, exposure is conditional. It depends on a specific iRule and profile combination, not just on running an affected version.

For context, F5 describes its portfolio as an Application Delivery and Security Platform that combines traffic management and security for applications and APIs, and states that more than 80 percent of the Fortune Global 500 rely on the company. That figure is F5's own adoption claim rather than an independent market share measurement.

Technical Information

Root cause

F5 classifies the bug as CWE-121: Stack-Based Buffer Overflow in TMM. The vulnerable component, per F5, is the MR::message route iRules command. The overflow is reached through TMM's data-plane handling of that command on a virtual server that also has an HTTP profile attached. F5 tracks the issue internally as bug IDs 2719437 and 2719617, covering BIG-IP and BIG-IP Next for Kubernetes.

F5 has not published a source diff, commit, or description of the code change. The fixes ship as closed-source engineering hotfixes. In general terms, a fix for a stack overflow of this kind means bounding or checking the data copied into a fixed-size stack buffer while the route command is processed. That is an inference from the CWE classification, not something F5 has confirmed.

Required configuration

All of the following must be true for a virtual server to be in scope:

  • The system runs an affected BIG-IP or BIG-IP Next for Kubernetes release (see below).
  • The virtual server has an HTTP profile attached.
  • The virtual server has an iRule that uses the MR::message route command.

F5 states there is no control-plane exposure. This is a data-plane issue only, and the attack surface is the listener of the affected virtual server rather than the management interfaces.

Attack flow

Based on the advisory, exploitation proceeds as follows:

  1. The attacker identifies a virtual server reachable over the network that is configured with an HTTP profile and an iRule invoking MR::message route. No authentication is required.
  2. The attacker sends undisclosed requests to that virtual server. F5 has not described the request format or which fields are involved.
  3. While TMM processes the request through the MR::message route command, data overflows a stack buffer.
  4. TMM terminates. Traffic handled by TMM is disrupted while the process restarts, producing a denial-of-service condition.
  5. F5 states the condition may lead to remote code execution. The advisory does not describe how reliably this can be achieved or what constraints apply.

Repeating step 2 after each restart would extend the outage. F5 frames the impact as traffic disruption during each TMM restart.

Exploitation status

The F5 advisory does not state that this CVE is exploited in the wild, does not identify an attacker, and does not describe a public proof of concept. A contemporaneous report from The Hacker News covering six related critical BIG-IP flaws noted that none of the advisories stated the flaws had been exploited. The material we reviewed does not establish a CISA Known Exploited Vulnerabilities catalog listing for this CVE. None of this proves exploitation is absent. It only means the sources do not report it.

Patch Information

F5 fixed CVE-2026-120292 with engineering hotfixes (EHFs), released on November 18, 2026 and available on the MyF5 Downloads page. F5 lists the mitigation as None. The advisory gives no configuration workaround or interim mitigation, so installing a fixed build is the only remediation F5 offers. It does not recommend disabling the iRule, altering the HTTP profile, or applying a network filter, and those should not be treated as F5-approved mitigations.

Fixed builds

  • BIG-IP (all modules) 21.x, vulnerable 21.1.0: BIGIP-21.1.0.4.0.19.3-ENG
  • BIG-IP 17.5.x, vulnerable 17.5.0 through 17.5.1: BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG
  • BIG-IP 17.1.x, vulnerable 17.1.0 through 17.1.3: BIGIP-17.1.3.7.0.21.4-ENG or BIGIP-17.1.3.6.0.14.20-ENG
  • BIG-IP Next for Kubernetes 2.4.x, vulnerable 2.4.0 through 2.4.2: BNK-2.4.2-EHF1
  • BIG-IP Next for Kubernetes 2.3.x, vulnerable 2.3.0 through 2.3.4: BNK-2.3.4-EHF1
  • BIG-IP Next for Kubernetes 2.2.x, vulnerable 2.2.0 through 2.2.5: BNK-2.2.5-EHF1

Choosing the right build

Some branches have two fixed builds, each rebased on a different starting point. Pick the one that matches what is already installed. F5's guidance in K000164239:

  • BIGIP-17.1.3.6.0.14.20-ENG: if you are running EHF BIGIP-17.1.3.6.0.9.20-ENG.
  • BIGIP-17.1.3.7.0.21.4-ENG: if you are on the 17.1.3.7 base release or earlier.
  • BIGIP-17.5.1.10.0.80.35-ENG: if you are running EHF BIGIP-17.5.1.10.0.7.35-ENG or BIG-IP-17.5.1.10.0.37.35-ENG.
  • BIGIP-17.5.1.11.0.61.12-ENG: if you are on the 17.5.1.11 base release or earlier.
  • BIGIP-21.1.0.4.0.19.3-ENG: if you are on the 21.1.0.4 base release or earlier.

If you run a custom engineering hotfix, none of these builds apply. F5 asks you to contact F5 Support for a new EHF that includes this fix. Otherwise a generic build could silently drop your existing custom fixes, or you could remain unpatched.

Caveats

  • F5 warns that EHFs do not undergo the extensive QA of scheduled releases and are provided without a warranty or guarantee of usability. Stage them before rolling them out broadly.
  • Per F5's versioning policy, once a fix lands in a branch, all later releases in that branch include it. Watch for a regular maintenance release that supersedes these EHFs.
  • Review the special considerations F5 published for the November 18, 2026 engineering hotfixes before deployment.

Affected Systems and Versions

Affected, per F5:

  • BIG-IP: 21.1.0
  • BIG-IP: 17.5.0 through 17.5.1
  • BIG-IP: 17.1.0 through 17.1.3
  • BIG-IP Next for Kubernetes: 2.4.0 through 2.4.2
  • BIG-IP Next for Kubernetes: 2.3.0 through 2.3.4
  • BIG-IP Next for Kubernetes: 2.2.0 through 2.2.5

Vulnerable configuration: a virtual server with an HTTP profile and an iRule using MR::message route. F5 does not describe systems on an affected version that lack this combination as exposed to this issue.

F5 lists these products as not vulnerable: BIG-IP CNF, BIG-IQ, F5 Insight, F5 Distributed Cloud, NGINX, F5OS, and F5 AI Gateway.

Versions that have reached End of Technical Support (EoTS) were not evaluated, so the advisory does not establish their status either way.

Vendor Security History

The most relevant item in F5's recent record is the security incident disclosed in its October 2025 SEC filing. F5 stated that on August 9, 2025, it learned an unnamed nation-state actor had gained persistent access to certain systems, including the BIG-IP product development environment and engineering knowledge management platform. F5 said exfiltrated files included some BIG-IP source code and information about undisclosed BIG-IP vulnerabilities, and that some files contained configuration or implementation information for a small percentage of customers.

At the time, F5 said it had no evidence of software supply chain modification and was not aware of active exploitation of undisclosed F5 vulnerabilities. We include this as background only. The sources reviewed do not link that incident to CVE-2026-120292.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization