Protect.Computer
NEWS

F5 Warns of Six Critical BIG-IP Flaws That Can Crash Traffic

· 3 min read · Network safety Device safety
F5 Warns of Six Critical BIG-IP Flaws That Can Crash Traffic

F5 disclosed six critical vulnerabilities in BIG-IP on November 18 that let an attacker crash the Traffic Management Microkernel (TMM) without logging in, disrupting traffic until TMM restarts, The Hacker News reports. F5 says the flaws may also allow remote code execution. They are stack-based buffer overflows in the data plane, the part of BIG-IP that handles almost all network traffic; F5 says the management side is not exposed. F5 rates all six 9.8 on CVSS v3.1 and 9.3 on CVSS v4.0.

Each flaw needs a particular configuration on a virtual server: an iRule using one specific command, or an APM policy that combines two kinds of agent. Five are in iRules and one is in APM. The Hacker News says none of F5’s advisories reports exploitation. WatchTowr researcher Sina Kheirkhah reported four of them, and F5 found the other two itself. The company lists no workaround, and the only fixes for these six are engineering hotfixes, which F5 warns “do not undergo the extensive QA assessment of scheduled software releases.” This is a separate set from CVE-2026-94127, the APM flaw that was exploited after F5’s September disclosure.

How to check if you’re affected

Affected products are BIG-IP systems (and BIG-IP Next for Kubernetes or BIG-IP CNF, where noted) that use the setups below on a virtual server. The Hacker News lists them as:

  • CVE-2026-123637: an APM per-request policy that includes both the Client Information agent and Endpoint Security agents. BIG-IP APM only.
  • CVE-2026-121805: an iRule using PEM::subscriber on client traffic. BIG-IP PEM, BIG-IP Next for Kubernetes and, as of November 18, BIG-IP CNF.
  • CVE-2026-120292: an HTTP profile plus an iRule using MR::message route. All BIG-IP modules and BIG-IP Next for Kubernetes.
  • CVE-2026-120285: an HTTP profile plus an iRule using PSC::ip_address. All BIG-IP modules, BIG-IP Next for Kubernetes and, as of November 18, BIG-IP CNF.
  • CVE-2026-116953: an iRule using GENERICMESSAGE::route on client traffic. All BIG-IP modules and BIG-IP Next for Kubernetes.
  • CVE-2026-120722: an iRule using DNS::scrape on client traffic. BIG-IP DNS and BIG-IP Next for Kubernetes.

Searching your iRules for those commands, and your APM per-request policies for that agent pairing, is our suggestion for finding exposure; the sources do not describe a check script.

For fixes, The Hacker News reports BIG-IP Next for Kubernetes is fixed in BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 and BNK-2.2.5-EHF1 (for versions 2.4.0-2.4.2, 2.3.0-2.3.4 and 2.2.0-2.2.5), and CNF in CNF-2.4.2-EHF1, CNF-2.3.4-EHF1 and CNF-2.2.5-EHF1 for CVE-2026-121805 and CVE-2026-120285. A system already on a custom engineering hotfix needs a new one from F5 support. F5 only assesses versions still in technical support, so a release missing from its tables has not been shown to be safe. Take the hotfix builds for classic BIG-IP from F5’s advisories, which did not render for us.

The Hacker News notes F5’s advisory lists BIG-IP CNF as not vulnerable while its CVE record, updated November 18, lists CNF as affected; check CNF against the CVE record.

F5’s notification also covers lower-rated flaws. One example reported by The Hacker News is CVE-2026-125274 (iControl SOAP, CVSS 8.8), fixed in BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6 and in BIG-IQ 8.4.2.3. Until patched, F5’s SOAP advisory explains how to limit iControl SOAP access to trusted networks.

Related earlier coverage: F5 Patches BIG-IP APM Zero-Day Actively Exploited for OAuth Server RCE and, from the same F5 release day, NGINX2Root: HTTP/2 Flaw CVE-2026-123007 Allows Code Execution.

Sources

Related reading