# F5 patches six critical BIG-IP data-plane overflows with hotfixes only. Check your iRules and APM policies

> F5's November 18 advisories cover six unauthenticated stack overflows (CVSS 9.8) that crash BIG-IP's traffic engine and may allow code execution in specific setups. There is no workaround and the fixes are engineering hotfixes, so knowing whether your configuration is exposed matters.

Published Nov 20, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/f5-big-ip-six-critical-tmm-overflows-cve-2026-123637-hotfix-only-what-to-check

F5 on November 18 published fixes for **six critical stack-based buffer overflows** in BIG-IP's Traffic Management Microkernel (TMM), the data-plane process that actually moves customer traffic. All six are rated **CVSS 9.8 (v3.1) / 9.3 (v4.0)**, need no authentication, and let a remote attacker crash TMM. According to the CVE records, they "may lead to" remote code execution.

Why it matters: BIG-IP is a common front door for enterprise apps, and a BIG-IP APM bug disclosed in September was later exploited. The catch this time is that every one of the six is only reachable in a **specific configuration** — mostly an iRule using a particular command — and F5's fix is an engineering hotfix rather than a regular release. So the useful first step is working out whether your config is in scope.

## Is anyone exploiting it?

Not as far as anyone has reported. The Hacker News says none of F5's advisories mark the flaws as exploited, and Daily CyberSecurity says none were in CISA's Known Exploited Vulnerabilities catalog at publication. The CVE Watchtower page for CVE-2026-120292 lists no confirmed exploitation and a 30-day EPSS score of 0.72%.

That said, the last big BIG-IP APM bug, CVE-2026-94127, was disclosed in September and was later exploited, The Hacker News notes, landing in KEV.

Four of the six were reported by **Sina Kheirkhah of watchTowr**. F5 found the PEM::subscriber and DNS::scrape bugs itself, per both outlets.

## The six critical flaws and what triggers them

| CVE | Exposed if… | Products named |
|---|---|---|
| CVE-2026-123637 | APM is provisioned and a per-request policy with both the Client Information and Endpoint Security agents is on a virtual server | BIG-IP APM |
| CVE-2026-120292 | A virtual server has an HTTP profile and an iRule using `MR::message route` | All BIG-IP modules, BIG-IP Next for Kubernetes |
| CVE-2026-120285 | HTTP profile plus an iRule using `PSC::ip_address` | All modules, BIG-IP Next for Kubernetes, CNF* |
| CVE-2026-116953 | An iRule using `GENERICMESSAGE::route` on client traffic | All modules, BIG-IP Next for Kubernetes |
| CVE-2026-120722 | An iRule using `DNS::scrape` on client traffic | BIG-IP DNS, BIG-IP Next for Kubernetes, CNF* |
| CVE-2026-121805 | An iRule using `PEM::subscriber` on client traffic | BIG-IP PEM, BIG-IP Next for Kubernetes, CNF* |

*CNF status is inconsistent across sources. The Hacker News says F5 updated the records to list CNF as affected for CVE-2026-121805 and CVE-2026-120285, and that the CVE record for CVE-2026-120722 lists CNF as affected even though the advisory says it is not; Daily CyberSecurity says CNF is not affected. If you run BIG-IP CNF, treat it as potentially exposed until F5's advisory pages say otherwise.

F5 describes these as a "data plane issue only" — the management interface is not the attack path. Affected BIG-IP branches are **21.1.0, 17.5.0–17.5.1 and 17.1.0–17.1.3**, and BIG-IP Next for Kubernetes **2.2.0–2.4.2**, per Daily CyberSecurity. F5's articles for two of the bugs are K000163937 (CVE-2026-123637) and K000163940 (CVE-2026-120292).

## What to do

1. **Search your iRules** for the five commands above. On a BIG-IP, listing the config and grepping works, for example:
   ```
   tmsh list ltm rule | grep -nE 'MR::message|PSC::ip_address|GENERICMESSAGE::route|DNS::scrape|PEM::subscriber'
   ```
   Then check whether those iRules are attached to virtual servers handling untrusted traffic.
2. **If you run APM**, review per-request policies for the Client Information plus Endpoint Security agent combination.
3. **If you're in scope, schedule the hotfix.** There is no mitigation or workaround. Daily CyberSecurity lists the BIG-IP engineering hotfixes as `BIGIP-21.1.0.4.0.19.3-ENG3`, `BIGIP-17.5.1.11.0.61.12-ENG3` and `BIGIP-17.1.3.7.0.21.4-ENG3`. For BIG-IP Next for Kubernetes the fixes are the 2.4.2, 2.3.4 and 2.2.5 EHF builds — The Hacker News writes them as EHF1, Daily CyberSecurity as EHF13, so confirm the exact build in F5's article before you download.
4. **Test before you roll out.** F5's own warning, quoted by The Hacker News, is that engineering hotfixes "do not undergo the extensive QA assessment of scheduled software releases."
5. **If you're not in scope**, you can wait for the next scheduled maintenance release — but re-check after any iRule change.

## Six more fixes in the same batch

The Hacker News also lists six lower-rated BIG-IP and BIG-IQ flaws fixed the same day. Most need authentication or specific APM/SAML settings:

| CVE | Component | CVSS 3.1 | Fixed in |
|---|---|---|---|
| CVE-2026-125274 | iControl SOAP | 8.8 | BIG-IP 21.1.0.3, 17.5.1.10, 17.1.3.6; BIG-IQ 8.4.2.3 |
| CVE-2026-120718 | iControl REST (tokens may not expire) | 8.1 | BIG-IP 21.1.0.2, 17.5.1.10, 17.1.3.6 |
| CVE-2026-125272 | APM, form-based Logon Page | 7.5 | Same hotfixes as the critical six |
| CVE-2026-126822 | APM as SAML SP | 7.5 | Same hotfixes; or remove the SAML Auth agent if unused |
| CVE-2026-126336 | APM SAML SP with encrypted assertions | 7.5 | BIG-IP 21.1.0.3, 17.5.1.10, 17.1.3.6 |
| CVE-2026-121812 | APM / SSL Orchestrator with policy tracing on (off by default) | 7.5 | Hotfixes; SSL Orchestrator on 21.1 and 17.1 only |

For the iControl REST token bug, Daily CyberSecurity says the workaround is to have scripts that create REST tokens delete them when they're done.

## What to watch

The risk changes if technical details or a proof of concept appear, which would make the vulnerable iRule patterns easy to probe for. Watch for CISA adding any of these CVEs to KEV, and for F5 folding the fixes into regular point releases so you don't have to run an engineering build.


## Sources

1. [The Hacker News — F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE](https://thehackernews.com/2026/11/f5-warns-6-critical-big-ip-flaws-can.html)
2. [Daily CyberSecurity — F5 BIG-IP Nov 2026 Update Fixes 7 Flaws, Incl. RCE CVE-2026-123637](https://securityonline.info/f5-big-ip-november-2026-update-7-flaws/)
3. [ThreatInt — CVE-2026-123637 record](https://cve.threatint.com/CVE/CVE-2026-123637)
4. [Daily CyberSecurity CVE Watchtower — CVE-2026-120292](https://securityonline.info/cve-watchtower/cve-2026-120292/)
