F5 Issues Hotfixes for Six Critical BIG-IP Traffic-Handling Flaws
F5 has disclosed six critical vulnerabilities in BIG-IP that can let unauthenticated attackers crash the Traffic Management Microkernel (TMM), interrupting traffic handled by affected virtual servers. The company says the flaws may also permit remote code execution. It released engineering hotfixes, but lists no workaround for the six issues while systems remain unpatched.
All six vulnerabilities are stack-based buffer overflows in the BIG-IP data plane, which processes most of the platform’s network traffic. F5 says the management plane is not exposed to these flaws. Each vulnerability requires a particular configuration on a virtual server, involving either an iRule command or an APM policy with specified agents. F5 rated each issue 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0.
A successful attack could crash TMM and disrupt traffic until the process restarts. The advisories do not report exploitation of these six vulnerabilities. Four were reported by WatchTowr researcher Sina Kheirkhah; F5 identified the other two.
Check virtual-server configurations and affected products
Five of the vulnerabilities involve iRules, which administrators use to control traffic handling. The remaining flaw affects the Access Policy Manager (APM) module. The required configuration and affected products differ by CVE:
- CVE-2026-123637: An APM per-request policy must contain both the Client Information agent and Endpoint Security agents. F5 lists BIG-IP APM as affected.
- CVE-2026-121805: A virtual server must use an iRule containing PEM::subscriber on client traffic. Affected products include BIG-IP PEM, BIG-IP Next for Kubernetes and BIG-IP CNF.
- CVE-2026-120292: The configuration requires an HTTP profile and an iRule using MR::message route. F5 lists all BIG-IP modules and BIG-IP Next for Kubernetes as affected.
- CVE-2026-120285: An HTTP profile and an iRule using PSC::ip_address are required. The affected-product list includes all BIG-IP modules, BIG-IP Next for Kubernetes and BIG-IP CNF.
- CVE-2026-116953: An iRule must use GENERICMESSAGE::route on client traffic. F5 lists all BIG-IP modules and BIG-IP Next for Kubernetes.
- CVE-2026-120722: An iRule must use DNS::scrape on client traffic. The affected products are BIG-IP DNS and BIG-IP Next for Kubernetes.
There is a discrepancy in F5’s CNF information: the advisory for CVE-2026-120285 says BIG-IP CNF is not vulnerable, while the CVE record, updated on the disclosure date, lists CNF as affected. Administrators should verify the latest product-specific guidance with F5 before concluding that a CNF deployment is unaffected.
Hotfixes are the only listed fixes
For the six critical flaws, F5 lists engineering hotfixes rather than fixes in scheduled software releases. The advisories provide no workaround pending installation. F5 cautions that engineering hotfixes do not receive the extensive quality-assurance assessment applied to scheduled releases. Its policy also states that they carry no warranty or promise of effectiveness. Customers running a custom engineering hotfix must obtain a new one from F5 support.
F5 lists fixes for BIG-IP Next for Kubernetes in BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 and BNK-2.2.5-EHF1, covering the respective 2.4.0–2.4.2, 2.3.0–2.3.4 and 2.2.0–2.2.5 version ranges. For CVE-2026-121805 and CVE-2026-120285, BIG-IP CNF fixes are CNF-2.4.2-EHF1, CNF-2.3.4-EHF1 and CNF-2.2.5-EHF1 for the corresponding version ranges. F5’s checks cover versions still within technical support; an older release omitted from its tables has not thereby been established as safe.
The disclosure should not be conflated with CVE-2026-94127, a separate APM heap-based buffer overflow disclosed by F5 on September 22. That earlier issue affected APM configurations operating as OAuth authorization servers and was later added to the U.S. Cybersecurity and Infrastructure Security Agency’s Known Exploited Vulnerabilities catalog. The six newly disclosed flaws are stack-based overflows with different configuration prerequisites.
Recommended response
Administrators should inventory BIG-IP virtual servers and determine whether the specific iRule commands or APM agent combination are present, then map those configurations to the affected products and versions. Because F5 lists no workaround for the critical vulnerabilities, prioritize validating and applying the relevant engineering hotfixes in line with the organization’s change and availability procedures. Teams should also review the CNF advisory and CVE record discrepancy directly with F5, and avoid treating unsupported versions as unaffected.