F5 Releases Engineering Hotfixes for Six Critical BIG-IP Flaws

F5 has disclosed six critical vulnerabilities in BIG-IP that can allow an unauthenticated attacker to crash the Traffic Management Microkernel (TMM), interrupting traffic until the process restarts. The company said the flaws may also enable remote code execution and assigned each a CVSS v3.1 score of 9.8 and a CVSS v4.0 score of 9.3.
The vulnerabilities are stack-based buffer overflows in BIG-IP’s data plane, which processes almost all network traffic. F5 said the management plane is not exposed. Its advisories do not report exploitation of any of the six flaws.
Specific virtual-server settings determine exposure
All six issues require a particular configuration on a virtual server. Five are associated with BIG-IP iRules, while one affects an Access Policy Manager (APM) per-request policy. Four vulnerabilities were reported by watchTowr researcher Sina Kheirkhah, and F5 identified the remaining two.
- CVE-2026-123637 affects BIG-IP APM when a per-request policy contains both Client Information and Endpoint Security agents.
- CVE-2026-121805 affects PEM configurations using the PEM::subscriber iRule command on client traffic, as well as BIG-IP Next for Kubernetes and BIG-IP CNF.
- CVE-2026-120292 requires an HTTP profile and an iRule using MR::message route.
- CVE-2026-120285 requires an HTTP profile and an iRule using PSC::ip_address.
- CVE-2026-116953 involves GENERICMESSAGE::route on client traffic, while CVE-2026-120722 involves DNS::scrape on client traffic.
The affected product scope differs by CVE. Several flaws reach BIG-IP Next for Kubernetes, while CVE-2026-121805 and CVE-2026-120285 also affect BIG-IP CNF. F5’s advisory lists CNF as not vulnerable in one place, but the updated CVE records list it as affected.
Hotfixes are the only listed remediation
F5 lists no workaround for the six critical issues. The available remediation is an engineering hotfix, a build issued between normal releases. F5 cautions that these hotfixes do not receive the extensive quality-assurance assessment applied to scheduled releases, and systems running a custom engineering hotfix require a replacement hotfix from F5 Support.
For BIG-IP Next for Kubernetes versions 2.4.0 through 2.4.2, 2.3.0 through 2.3.4, and 2.2.0 through 2.2.5, the fixes are BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, and BNK-2.2.5-EHF1 respectively. For the two affected CNF issues, the corresponding fixes are CNF-2.4.2-EHF1, CNF-2.3.4-EHF1, and CNF-2.2.5-EHF1.
Additional BIG-IP and BIG-IQ advisories
F5 also issued six lower-rated advisories. They include CVE-2026-125274, an iControl SOAP issue scored 8.8 that may let a network-accessible Guest-role user issue unauthorized management requests, and CVE-2026-120718, an 8.1-rated iControl REST token-expiration issue. The company also described several 7.5-rated APM and SAML conditions that can crash TMM without authentication.
F5 evaluates only releases within technical support, so versions absent from its tables have not been established as safe. Organisations should identify supported BIG-IP, BIG-IP Next for Kubernetes, and CNF deployments; review virtual-server iRules and APM policies for the listed conditions; and schedule the applicable engineering hotfixes with testing and support arrangements because no workaround is available for the critical flaws.

