Hotfixes are now available for at least five critical F5 BIG-IP flaws that can crash the Traffic Management Microkernel and, the company says, may allow remote code execution. The Canadian Centre for Cyber Security listed the affected products on 19 November 2026, a day after F5 published advisory K000163937.
The bugs sit in the data plane, the part of a BIG-IP system that handles almost all of its network traffic, and they matter only on virtual servers with particular iRule commands or a particular Access Policy Manager set-up. F5 has described no workaround. The fix, for the critical issues, is a set of engineering hotfixes rather than a scheduled software release. None of the company’s advisories, as reported in the trade press, says these F5 BIG-IP flaws have been used in attacks, and they were still absent from CISA’s Known Exploited Vulnerabilities catalogue when TSN checked on 20 November.
In brief
- The Canadian Cyber Centre lists the products affected by the F5 BIG-IP flaws, including BIG-IP (with APM, SSL Orchestrator and PEM), BIG-IP CNF, BIG-IP Next for Kubernetes, and BIG-IQ Centralized Management.
- F5, as quoted by BleepingComputer, says a remote unauthenticated attacker can cause a denial of service “and may perform RCE,” and that “there is no control plane exposure; this is a data plane issue only.”
- Press counts of the critical bugs differ, so this article says at least five. The flaws are not known to be exploited and are not in CISA’s KEV catalogue, version 2026.11.18.
Canada lists the affected BIG-IP and BIG-IQ product lines
The Cyber Centre’s alert, serial AV26-1178, opens with a simple statement: “As of November 18, 2026, F5 is affected by vulnerabilities” in a named set of products. For BIG-IP, BIG-IP APM, SSL Orchestrator and PEM, it lists version 17.1.0 prior to the engineering build BIGIP-17.1.3.7.0.21.4-ENG, 17.5.0 prior to BIGIP-17.5.1.11.0.61.12-ENG, and 21.1.0 prior to BIGIP-21.1.0.4.0.19.3-ENG. For BIG-IP CNF it lists 2.2.0, 2.3.0 and 2.4.0 prior to the CNF-2.2.5-EHF1, CNF-2.3.4-EHF1 and CNF-2.4.2-EHF1 builds. For BIG-IP Next for Kubernetes the equivalent fixed builds are BNK-2.2.5-EHF1, BNK-2.3.4-EHF1 and BNK-2.4.2-EHF1. BIG-IQ Centralized Management is listed as affected prior to 8.4.2.3.
The same alert points administrators to six F5 knowledge-base articles and CVE identifiers: CVE-2026-123637, CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953 and CVE-2026-120722. It does not itself attach a severity rating to each identifier. The Hacker News, in an 18 November report, describes all six as critical and says the company rates them 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0. BleepingComputer, writing on 20 November, counted five critical CVEs, leaving out CVE-2026-120722, and separately described a high-severity SAML denial-of-service issue, CVE-2026-126822. Because those tallies differ, TSN is using the Cyber Centre’s product list and saying at least five critical flaws.
The Cyber Centre encourages users and administrators to review F5’s links and apply any necessary updates.
The F5 BIG-IP flaws need specific iRule or APM setups
BleepingComputer quotes F5 as saying: “Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may perform RCE.” In the same report, the company adds: “There is no control plane exposure; this is a data plane issue only.” BleepingComputer also reports that F5 has no mitigation measures and has told teams to install the out-of-band hotfixes.
The Hacker News, drawing on the same advisories, says the issues are stack-based buffer overflows, and that each one needs a specific configuration on a virtual server. Five of the six, in that account, involve iRules that use particular commands: PEM::subscriber, MR::message route, PSC::ip_address, GENERICMESSAGE::route, or DNS::scrape. The remaining one, CVE-2026-123637, is described as affecting BIG-IP APM only, when a per-request policy includes both the Client Information agent and Endpoint Security agents. The Hacker News says watchTowr researcher Sina Kheirkhah reported four of the flaws and that F5 found the other two itself. Those are configuration conditions, not a list of steps for using the bugs, and only systems that actually have those set-ups are described as vulnerable.
The same 18 November F5 publication batch, The Hacker News notes, included ten advisories for NGINX, which F5 also owns. That sits alongside the HTTP/2 memory-safety fixes nginx.org issued the same day in 1.30.7 and 1.31.9, a separate set of bugs. For operators who run other front-door traffic software, Apache’s 2.4.71 HTTP/2 remote-code-execution fix is the nearest recent parallel in a different product.
Engineering hotfixes close a hole that scheduled releases have not yet reached
The operational message is narrower than a blanket “patch every BIG-IP.” Administrators first need to know whether a virtual server is running one of the named iRule commands, or the APM policy pairing, on a version the Cyber Centre has listed as affected by the F5 BIG-IP flaws. If it is, the only fix described for the critical issues is an engineering hotfix. The Hacker News reports that F5 warns those builds skip the extensive quality assessment given to scheduled software releases, and that its hotfix policy gives no warranty they will work. A device already on a custom engineering hotfix, in that account, needs a fresh one from F5’s support team. The Hacker News also notes that F5 checks only versions still inside technical support, so an older release missing from the tables has not been shown to be safe.
That is a more awkward fix than a normal maintenance window, and it is the one on offer. There is no official workaround to sit behind, and a Traffic Management Microkernel restart is, by F5’s own description, a traffic outage. For UK operators of these product versions, the same configuration check and the same hotfix apply; TSN has not seen a separate UK advisory.
The exposure picture should be handled with care. BleepingComputer reports that the internet threat watchdog Shadowserver “currently tracks more than 177,000 BIG-IP instances and over 14,600 IP addresses with BIG-IP APM fingerprints exposed online,” and immediately adds that there is no information on how many of those are honeypots or have already been patched. Those figures are Shadowserver’s, as reported by BleepingComputer. They are not a count of systems that are vulnerable to this week’s flaws.
Nor is a critical vendor advisory the same as a KEV listing. TSN checked CISA’s catalogue on 20 November 2026: version 2026.11.18, released at 19:17:41 GMT on 18 November, still has 1,786 entries and does not include CVE-2026-123637 or the other identifiers listed for these F5 BIG-IP flaws. A different BIG-IP APM bug, CVE-2026-94127, was added on 22 September 2026; The Hacker News is careful to say this week’s issues are a different class of overflow and need different settings. The Canadian Cyber Centre has flagged other edge-device bugs in recent weeks, including a Zyxel GS1900 vulnerability it described as possibly exploited. That earlier alert is not about BIG-IP, but it is a reminder that a national CSIRT listing and a KEV listing are different instruments.
The next thing to watch is whether CISA adds any of the F5 BIG-IP flaws to the catalogue, and whether F5 folds the engineering hotfixes into a scheduled release that has been through the usual quality process. Until then, the work is to check the named configurations and install the hotfixes if they apply.
Sources
- Canadian Centre for Cyber Security, F5 security advisory (AV26-1178), 19 November 2026
- F5, K000163937: BIG-IP APM vulnerability CVE-2026-123637, 18 November 2026
- The Hacker News, “F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE,” 18 November 2026
- BleepingComputer, “F5 releases emergency patches for critical BIG-IP RCE flaws,” 20 November 2026
- CISA Known Exploited Vulnerabilities catalogue, version 2026.11.18
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
- NGINX 1.30.7 and 1.31.9 Fix Two HTTP/2 Memory Flaws is the closest TSN account of the NGINX fixes F5’s group published in the same mid-November window, and the right next stop for operators who also run that stack.
- Apache HTTP Server 2.4.71 Fixes a Critical HTTP/2 RCE
- Canada Flags Zyxel GS1900 Vulnerability as Possibly Exploited
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X

