Alert

Logo de F5

Alert 2026-172 Six critical vulnerabilities in F5 BIG-IP with possible remote code execution

Affected product(s): 

Product (six critical TMM flaws)Affected versionsFix
BIG-IP 21.x21.1.0 (including the 21.1.0.4 base)BIGIP-21.1.0.4.0.19.3-ENG
BIG-IP 17.5.x17.5.0 to 17.5.1 (including the 17.5.1.11 base)BIGIP-17.5.1.11.0.61.12-ENG; if BIGIP-17.5.1.10.0.7.35-ENG or BIGIP-17.5.1.10.0.37.35-ENG is already in use, BIGIP-17.5.1.10.0.80.35-ENG
BIG-IP 17.1.x17.1.0 to 17.1.3 (including the 17.1.3.7 base)BIGIP-17.1.3.7.0.21.4-ENG; if BIGIP-17.1.3.6.0.9.20-ENG is already in use, BIGIP-17.1.3.6.0.14.20-ENG
BIG-IP Next for Kubernetes 2.x2.4.0 to 2.4.2, 2.3.0 to 2.3.4 and 2.2.0 to 2.2.5 (five of the six; not CVE-2026-123637)BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 or BNK-2.2.5-EHF1
BIG-IP CNF 2.x2.4.0 to 2.4.2, 2.3.0 to 2.3.4 and 2.2.0 to 2.2.5, only CVE-2026-120285 and CVE-2026-121805CNF-2.4.2-EHF1, CNF-2.3.4-EHF1 or CNF-2.2.5-EHF1
CVECondition on the virtual serverScope
CVE-2026-116953iRule that processes client traffic with GENERICMESSAGE::routeAll modules
CVE-2026-120285HTTP profile and an iRule with PSC::ip_addressAll modules
CVE-2026-120292HTTP profile and an iRule with MR::message routeAll modules
CVE-2026-120722iRule that processes client traffic with DNS::scrapeBIG-IP DNS only
CVE-2026-121805iRule that processes client traffic with PEM::subscriberBIG-IP PEM only
CVE-2026-123637APM provisioned and a per-request policy with the Client Information and Endpoint Security agentsBIG-IP APM only
Product (iControl SOAP)Affected versionsFix
BIG-IP (all modules), CVE-2026-12527421.1.0, 17.5.0 to 17.5.1 and 17.1.0 to 17.1.321.1.0.3, 17.5.1.10 or 17.1.3.6
BIG-IQ Centralized Management8.4.0 to 8.4.28.4.2.3

Only systems with the configuration listed for each CVE are exposed. The vendor does not evaluate branches that have already reached the end of technical support; a branch that does not appear in the tables is not declared safe. BIG-IQ, F5OS, NGINX, F5 Distributed Cloud and F5 AI Gateway are not vulnerable to the six critical flaws. CVE-2026-125274 does not affect BIG-IP Next for Kubernetes or CNF.

Description

Six critical vulnerabilities have been reported in F5 BIG-IP, identified as CVE-2026-116953, CVE-2026-120285, CVE-2026-120292, CVE-2026-120722, CVE-2026-121805 and CVE-2026-123637. The vendor made them public on Nov 18, 2026 at 12:00 p.m. (PYT) and assigns them CVSS 9.8, critical; it also publishes CVSS 9.3, critical. This bulletin is classified as CRITICAL. They are stack-based buffer overflows in the TMM (Traffic Management Microkernel), on the data plane. Undisclosed requests, sent without authentication to a virtual server with the affected configuration, cause the TMM to terminate; traffic is disrupted while it restarts and, according to the vendor, the flaw may lead to remote code execution. There is no control-plane exposure.

Each of the six requires a specific configuration on a virtual server, detailed under Affected product(s). Without that configuration, the system is not exposed to that CVE. Three affect all modules; CVE-2026-120722 affects only BIG-IP DNS, CVE-2026-121805 only BIG-IP PEM and CVE-2026-123637 only BIG-IP APM. BIG-IP Next for Kubernetes is affected in five of the six (not in CVE-2026-123637). BIG-IP CNF, according to the vendor advisories, is affected only in CVE-2026-120285 and CVE-2026-121805.

The fix for the six is an engineering hotfix (EHF). The vendor does not publish a scheduled release or a temporary measure for those flaws. It warns that EHFs do not undergo the full quality assessment of a scheduled release and are delivered with no warranty. The specific build is chosen according to the version or EHF already installed, following guide K000164239. Anyone using a custom EHF must request a new one from the vendor’s support.

In the same out-of-cycle batch, CVE-2026-125274 was published, an injection in iControl SOAP. The vendor assigns it CVSS 8.8, high, and also CVSS 8.7, high. An authenticated iControl SOAP user, with at least the Guest role, can inject an unauthorized management request and, according to the vendor, execute system commands, create or delete files, or disable services. This is a control-plane issue only, with no data-plane exposure. It is fixed in regular releases (not with the hotfix for the six) and the vendor does publish a temporary measure, described in Mitigation. It affects BIG-IP (all modules) and BIG-IQ Centralized Management.

The vendor does not report that these flaws have been used in real attacks. No public proof of concept was located. The Nov 18, 2026 batch includes other advisories, among them the NGINX HTTP/2 issues covered in Alert 2026-170, which are not the subject of this bulletin. As context, not as the same flaw, CVE-2026-94127, a distinct BIG-IP APM vulnerability disclosed on Sep 22, 2026, was used in real attacks.

Mitigation

Inventory BIG-IP, BIG-IP Next for Kubernetes, BIG-IP CNF and BIG-IQ systems, with the version and, if applicable, the installed EHF. Identify virtual servers with iRules that use GENERICMESSAGE::route, PSC::ip_address, MR::message route, DNS::scrape or PEM::subscriber (and whether they have an HTTP profile), and APM per-request policies with the Client Information and Endpoint Security agents. That review can be done from the management console or with iHealth, which the vendor offers to diagnose these CVEs.

The fix for the six critical flaws is to install the matching engineering hotfix, according to K000164239, starting with internet-reachable systems that have those configurations. Test it first in a non-production environment, if possible, because of the vendor’s quality warning. In high availability, update one member at a time to reduce disruption. The vendor does not publish a temporary measure for those six flaws. If the hotfix cannot yet be applied, assess whether the affected iRule or APM agent is essential: that reduces exposure, but it is not an official temporary measure.

For CVE-2026-125274, update to the regular releases listed in Solution. Until then, the vendor states that there is no mitigation that also allows iControl SOAP access for users who are not fully trusted. As a temporary measure, restrict iControl SOAP to trusted networks or devices: on self IPs, set Port Lockdown to “Allow None” or “Allow Custom” while blocking the iControl SOAP port (TCP 443 by default; on single-NIC VE instances, TCP 8443), and restrict the management interface to trusted users and networks. The vendor warns that blocking that access on self IPs can prevent use of the Configuration utility and of iControl, and can even break high-availability configurations and other services.

Watch for unexpected TMM restarts and traffic outages. The patch does not undo a prior compromise. The vendor has not published indicators of compromise.

Solution

The solution for the six critical vulnerabilities is to install the engineering hotfix that matches the version or EHF already installed, according to guide K000164239: BIGIP-21.1.0.4.0.19.3-ENG; BIGIP-17.5.1.11.0.61.12-ENG or, if a 17.5.1.10 EHF is already in use, BIGIP-17.5.1.10.0.80.35-ENG; BIGIP-17.1.3.7.0.21.4-ENG or, if BIGIP-17.1.3.6.0.9.20-ENG is already in use, BIGIP-17.1.3.6.0.14.20-ENG. On BIG-IP Next for Kubernetes, BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 or BNK-2.2.5-EHF1. On BIG-IP CNF, only for CVE-2026-120285 and CVE-2026-121805, CNF-2.4.2-EHF1, CNF-2.3.4-EHF1 or CNF-2.2.5-EHF1. Anyone using a custom EHF must request a new one from the vendor’s support.

For CVE-2026-125274, update BIG-IP to 21.1.0.3, 17.5.1.10 or 17.1.3.6, and BIG-IQ to 8.4.2.3. Those regular releases do not replace the hotfix for the six critical flaws: a system on 21.1.0.3, 17.5.1.10 or 17.1.3.6 still needs the EHF for its branch if it is exposed to any of the six.

For information on how to update, visit the following link:

https://my.f5.com/manage/s/article/K000164058

Additional information: