F5 Warns of Six Critical BIG-IP Flaws That Can Crash Traffic and Possibly Allow Remote Code Execution
F5 has disclosed six critical vulnerabilities in its BIG-IP products. Each allows an attacker without a login to crash the Traffic Management Microkernel (TMM), the component that processes almost all of BIG-IP's network traffic. Traffic is disrupted until the TMM restarts. F5 says the flaws may also allow remote code execution.
All six are stack-based buffer overflows and are rated 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0. They are not exposed on the management side, according to F5. Each one depends on a specific setup on a virtual server: five involve iRules that use a particular command, and one involves an APM policy that includes two particular kinds of agent. Some also affect BIG-IP Next for Kubernetes and BIG-IP CNF. WatchTowr researcher Sina Kheirkhah reported four of the flaws, and F5 found the other two itself. None of the advisories says the flaws have been exploited.
The fix is unusual. F5 has issued only engineering hotfixes, which are builds released between its normal software versions, and no workaround exists until one is installed. F5 warns that these hotfixes do not go through the extensive QA of scheduled releases and carry no warranty. Systems already on a custom engineering hotfix need a new one from F5 support. For BIG-IP Next for Kubernetes, fixes are BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 and BNK-2.2.5-EHF1. F5 only checks versions still in technical support, so an older release missing from its tables has not been shown to be safe.
These flaws are separate from CVE-2026-94127, an APM heap-based overflow disclosed on September 22 and later exploited, which CISA added to its Known Exploited Vulnerabilities catalog. F5's latest batch covers 22 advisories, including six lower-rated BIG-IP and BIG-IQ flaws.
Why it matters
Organisations running BIG-IP at the network edge face a patch decision with no easy option: no workaround exists, and the only fix is a hotfix F5 says lacks full QA and any warranty. Because exposure depends on specific iRule commands and APM agent combinations, a version check alone will not tell you if you are at risk; you need to audit configuration. The earlier APM flaw was exploited and added to CISA's catalog, so defenders cannot assume this class of bug will stay theoretical.
What to do
- Audit virtual servers for iRules and APM policies that match the configurations listed in F5's advisories.
- Request the relevant engineering hotfix from F5 support, and a new one if you already run a custom hotfix.
- Apply BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 or BNK-2.2.5-EHF1 on BIG-IP Next for Kubernetes, matching your version.
- Replace any release outside F5's technical support, since it has not been shown to be safe.