The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

F5 warns of six critical BIG-IP flaws including CVE-2026-123637

By The Daily Byte ·20 Nov 2026 ·5 min read
A data centre aisle lined with black server racks and network cabling, representing the network infrastructure F5 BIG-IP protects
F5 has disclosed six critical vulnerabilities in its BIG-IP application delivery platform that can crash traffic handling without an attacker needing to log in, and that may also allow remote code execution. The advisories were published on 18 November 2026, with engineering hotfixes released and no workaround available. All six are stack-based buffer overflows in BIG-IP's data plane, the part of the system that processes almost all network traffic, rated 9.8 under CVSS 3.1 and 9.3 under CVSS 4.0. An unauthenticated attacker who sends crafted requests to a vulnerable virtual server can terminate the Traffic Management Microkernel, known as TMM, disrupting traffic until it restarts. F5 says the flaws may also allow remote code execution, although none of the advisories reports that any of the six has been exploited. ## Which configurations are affected Each flaw only affects a virtual server with a particular configuration. Five of the six sit in iRules, the BIG-IP feature administrators use to manage traffic, and one sits in the BIG-IP APM access module. The affected setups are: - **CVE-2026-123637**: an APM per-request policy that includes both the Client Information agent and Endpoint Security agents. This affects BIG-IP APM only. - **CVE-2026-121805**: an iRule that uses PEM::subscriber on client traffic. This affects BIG-IP PEM, BIG-IP Next for Kubernetes and BIG-IP CNF. - **CVE-2026-120292**: an HTTP profile and an iRule that uses MR::message route. This affects BIG-IP in all modules and BIG-IP Next for Kubernetes. - **CVE-2026-120285**: an HTTP profile and an iRule that uses PSC::ip_address. This affects BIG-IP in all modules, BIG-IP Next for Kubernetes and BIG-IP CNF. - **CVE-2026-116953**: an iRule that uses GENERICMESSAGE::route on client traffic. This affects BIG-IP in all modules and BIG-IP Next for Kubernetes. - **CVE-2026-120722**: an iRule that uses DNS::scrape on client traffic. This affects BIG-IP DNS and BIG-IP Next for Kubernetes. F5's advisory lists BIG-IP CNF as not vulnerable, but the CVE record, updated on 18 November, lists CNF as affected. The management side of BIG-IP is not exposed by these flaws, according to F5. WatchTowr researcher Sina Kheirkhah reported four of the six, and F5 found the other two itself. ## Hotfix-only fixes, with a testing warning For the six critical flaws, the only fixes are engineering hotfixes, builds that F5 issues between its normal software releases. No scheduled release is listed as a fix, and the advisories provide no workaround until a hotfix is installed. F5 warns that engineering hotfixes do not undergo the extensive quality assessment of scheduled software releases, and its hotfix policy adds that they come with no warranty or promise that they will work. A system already running a custom engineering hotfix needs a new one from F5 support. BIG-IP Next for Kubernetes is fixed in builds BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 and BNK-2.2.5-EHF1, for versions 2.4.0 to 2.4.2, 2.3.0 to 2.3.4 and 2.2.0 to 2.2.5. BIG-IP CNF, on the same version ranges, is fixed 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. F5 checks only versions that are still within technical support, so an older release missing from its tables has not been shown to be safe. ## Six further flaws disclosed the same day F5's security notification lists 22 advisories published on 18 November, including 10 for NGINX, and the same day also brought six lower-rated flaws in BIG-IP and BIG-IQ. They include CVE-2026-125274, an iControl SOAP flaw rated 8.8, and CVE-2026-120718, an iControl REST flaw rated 8.1 in which tokens may not expire as expected. Today's flaws differ from CVE-2026-94127, an APM flaw F5 disclosed on 22 September 2026 that was later exploited and added to CISA's Known Exploited Vulnerabilities catalogue the same day. That flaw is a heap-based buffer overflow in APM setups serving as OAuth authorisation servers; today's six are stack-based overflows needing different settings. ## What BIG-IP owners should do Organisations running BIG-IP should check their virtual servers against the six configurations above and open a support case with F5 for the engineering hotfix that matches their version. Because the flaws are unauthenticated and sit in the data plane, exposed virtual servers should be treated as a priority even though no exploitation has been reported. Details of all six flaws are in F5's advisories, reported by [The Hacker News](https://thehackernews.com/2026/11/f5-warns-6-critical-big-ip-flaws-can.html), with an independent breakdown of the six configuration triggers from [Brandefense](https://brandefense.io/security-news/f5-big-ip-irule-vulnerabilities-2026/). ## Frequently asked questions **Are the F5 BIG-IP flaws being exploited?** No. None of F5's advisories reports exploitation, and they are not in CISA's Known Exploited Vulnerabilities catalogue. **Is there a workaround?** No. F5 lists no workaround for the six critical flaws; the only fix is the matching engineering hotfix. **Does my BIG-IP need patching if it does not use iRules?** Only virtual servers with one of the listed configurations are affected, so check the iRule commands and APM policies on each virtual server first.