Critical CVSS 9.8 Security news
F5 BIG-IP: six critical iRules and APM flaws can crash TMM without authentication and may allow code execution
F5 disclosed a batch of BIG-IP vulnerabilities on 18 November 2026. Six of them score 9.8 under CVSS 3.1: stack-based buffer overflows in TMM, the data-plane core, triggered by crafted traffic without authentication. The result is a TMM restart and a traffic outage, and F5 says remote code execution may be possible. Only devices with specific iRules commands or a particular APM policy are affected. Fixes are so far available only as engineering hotfixes, and F5 lists no workaround. No in-the-wild exploitation has been reported.
Key points
- Who is affected: F5 BIG-IP load balancers and VPN gateways on 17.1, 17.5 and 21.1, plus BIG-IP Next for Kubernetes – but only with specific configurations (iRules using certain commands, or an APM policy with the Client Information and Endpoint Security agents).
- The flaw: a stack-based buffer overflow (CWE-121) in TMM, the process that handles traffic. An unauthenticated attacker sends crafted requests, TMM crashes and restarts, and F5 says code execution may be possible.
- Exploited: not yet. At least three of the flaws were reported by Sina Kheirkhah of watchTowr, a firm that often publishes technical write-ups after patches ship, so details could surface soon.
- What to do: check whether you run an affected configuration, apply the F5 engineering hotfix and also patch iControl SOAP (CVE-2026-125274, command execution from a Guest account).
Vulnerabilities: CVE-2026-116953, CVE-2026-120285, CVE-2026-120292, CVE-2026-120722, CVE-2026-121805, CVE-2026-123637, CVE-2026-125274
What happened
On 18 November 2026 F5 published more than twenty CVE records covering BIG-IP, BIG-IQ, BIG-IP Next for Kubernetes and NGINX. The NGINX fixes are covered in a separate story. On BIG-IP, the most serious are six flaws scoring 9.8 under CVSS 3.1 (9.3 under CVSS 4.0), all of the same kind: a stack-based buffer overflow (CWE-121) in TMM (Traffic Management Microkernel), reachable without authentication through traffic to a virtual server.
| CVE | Vulnerable condition | F5 advisory |
|---|---|---|
| CVE-2026-116953 | iRule using GENERICMESSAGE::route |
K000163941 |
| CVE-2026-120285 | HTTP profile plus iRule using PSC::ip_address (PEM) |
K000163939 |
| CVE-2026-120292 | HTTP profile plus iRule using MR::message route |
K000163940 |
| CVE-2026-120722 | iRule using DNS::scrape |
K000163945 |
| CVE-2026-121805 | iRule using PEM::subscriber |
K000163946 |
| CVE-2026-123637 | APM per-request policy with the Client Information and Endpoint Security agents | K000163937 |
According to the CVE records, at least three of them (CVE-2026-116953, CVE-2026-120285 and CVE-2026-123637) were reported by Sina Kheirkhah of watchTowr.
Technical details
TMM is the process that handles all data-plane traffic on BIG-IP – load balancing, TLS, iRules and APM. F5's description says "undisclosed requests" against an affected configuration cause TMM to terminate. While TMM restarts, the device stops passing traffic, so at minimum the result is an outage. For all six flaws F5 adds that the crash "may lead to remote code execution". No account or user interaction is needed (vector AV:N/AC:L/PR:N/UI:N). F5 says the control plane (management) is not exposed.
The same batch also fixes control-plane bugs. The most serious is CVE-2026-125274 (CVSS 3.1 8.8) in iControl SOAP: an authenticated user with at least the Guest role can inject an unauthorised management request (CWE-93) and run system commands, create or delete files, or disable services. CVE-2026-120718 (8.1) means iControl REST tokens may not expire in some cases. Four further APM bugs (CVE-2026-121812, CVE-2026-125272, CVE-2026-126336, CVE-2026-126822; 7.5) only crash TMM – they involve the APM logon page, SAML SP policies and the tmm.access.policytrace debug key.
Who is affected
| Product | Affected branch | Fixed (six critical flaws) |
|---|---|---|
| BIG-IP | 21.1.x | hotfix BIGIP-21.1.0.4.0.19.3-ENG |
| BIG-IP | 17.5.x | hotfix BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG |
| BIG-IP | 17.1.x | hotfix 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 / 2.3 / 2.2 | BNK-2.4.2-EHF1 / BNK-2.3.4-EHF1 / BNK-2.2.5-EHF1 |
For CVE-2026-123637 the record lists only BIG-IP, not BIG-IP Next for Kubernetes. The iControl SOAP bug CVE-2026-125274 is fixed in the regular releases BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6 and BIG-IQ 8.4.2.3. F5 did not evaluate versions past End of Technical Support, so anyone still running them should assume they may be vulnerable too.
How to tell if you were compromised
F5 has published no indicators of compromise and reports no exploitation. Our suggestions on what to watch:
- Unplanned TMM restarts and traffic outages – TMM termination entries in
/var/log/ltmand new TMM core files. - Repeated crashes following requests from the same addresses to virtual servers with affected iRules or an APM policy.
- For iControl SOAP: unexpected management changes in the audit log (
/var/log/audit) made by low-privilege accounts, new files or stopped services.
What to do
- Check whether you run an affected configuration. List your iRules on BIG-IP and search for the affected commands, for example
tmsh list ltm rule | grep -E "GENERICMESSAGE::route|PSC::ip_address|MR::message route|DNS::scrape|PEM::subscriber". In APM, review per-request policies for the Client Information and Endpoint Security agents. - Apply the hotfix listed in the relevant F5 advisory (K000163937 to K000163946). F5 lists no workaround for the critical flaws – if you don't need the affected command in an iRule, removing it also removes the vulnerable condition.
- Patch iControl SOAP (CVE-2026-125274) to 21.1.0.3, 17.5.1.10 or 17.1.3.6. Until then, F5 advises removing access for untrusted users, restricting SOAP on self IPs (Port Lockdown) and limiting management access.
- Delete unneeded iControl REST tokens (CVE-2026-120718) – according to F5, deleting a token stops its lifetime from being extended.
- Watch F5's advisories and the CISA KEV catalogue – exploitation often follows quickly once technical write-ups appear.
Timeline
Update
- 18 Nov 2026: first version.
FAQ
I run BIG-IP. Am I automatically vulnerable?
No. The six critical flaws need a specific configuration: a virtual server with an iRule that uses GENERICMESSAGE::route, PSC::ip_address, MR::message route, DNS::scrape or PEM::subscriber, or APM with a per-request policy containing the Client Information and Endpoint Security agents. If you use none of these, the critical flaws don't apply, but the iControl SOAP and REST bugs affect every installation.
Why does F5 list hotfixes rather than a new release?
For the six critical flaws, the CVE records list only builds with an ENG suffix (engineering hotfixes) as fixed, such as BIGIP-17.1.3.7.0.21.4-ENG. No regular maintenance release is listed yet. You get the hotfix through F5 support, as described in the relevant K article.
Does a data-plane flaw matter if my management interface is isolated?
Yes. These flaws are reachable through traffic to virtual servers, which is typically internet-facing. Isolating management only helps with the iControl SOAP and REST bugs, which sit on the control plane.
Sources
Spotted a mistake? Let us know and we will correct it openly.