F5 has uncovered six severe vulnerabilities in its BIG-IP platform capable of crashing the Traffic Management Microkernel (TMM) and potentially permitting remote code execution (RCE), even without user authentication. Each flaw achieves impact only under specific configurations, such as the use of certain iRule commands or particular APM (Access Policy Manager) agent combinations. Engineering hotfixes are now available; no workarounds are listed. CVSS scores place all six in the “Critical” category (9.8 for CVSS v3.1, and 9.3 under v4.0).
Which Configurations Are at Risk
The vulnerabilities are buffer overflows in BIG-IP’s data plane — the component that handles most network traffic — while the management plane reportedly remains unaffected. Five of the flaws stem from specific iRules commands, and one involves the APM module with a particular agent pairing. Affected modules include BIG-IP across all types, its Kubernetes-oriented edition (Next for Kubernetes), and its Cloud-Native Edition (CNF).
The six critical vulnerabilities break down as follows:
- CVE-2026-123637: Triggers when a virtual server uses a per-request policy with both the Client Information and the Endpoint Security agents in APM.
- CVE-2026-121805: Requires an iRule using PEM::subscriber on client traffic.
- CVE-2026-120292: An HTTP profile paired with an iRule that employs MR::message route.
- CVE-2026-120285: An HTTP profile with an iRule using PSC::ip_address.
- CVE-2026-116953: Involves using GENERICMESSAGE::route in an iRule handling client traffic.
- CVE-2026-120722: A virtual server using DNS::scrape in its iRule on client traffic.
Patch Status & Other High-Risk Flaws
F5 has released engineering hotfixes for all six critical issues. These fixes are designed to be deployed outside the regular software release cadence and thus do not undergo the same quality assurance or warranty assurances. Users on custom engineering hotfixes will require new hotfixes issued via F5 support. Specific Kubernetes-oriented versions and CNF branches have received hotfix updates for some of the bugs, including versions BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, and BNK-2.2.5-EHF1. CNF-2.4.2-EHF1, CNF-2.3.4-EHF1, and CNF-2.2.5-EHF1 also patch vulnerabilities like CVE-2026-121805 and CVE-2026-120285.
Beyond these, six additional BIG-IP and BIG-IQ vulnerabilities have been called out, each rated lower in severity but still serious. These include misconfigurations in APM access profiles, SAML-based SP agents, and an iControl REST issue where tokens may not expire properly. Some of them allow for DoS via TMM crashes, while others could enable unauthorized actions. Fixes or workarounds are supplied for these in the same set of hotfixes or via version-specific patches.
Why These Flaws Matter
BIG-IP by F5 is widely used by enterprises and carriers to manage traffic, balance loads, handle DNS requests, and enforce security policies, especially at the network perimeter and in cloud environments. Any bug that causes TMM to crash can disrupt traffic flow until the component is restarted — effectively bringing down services. Remote code execution, especially without needing to log in, might allow attackers to take control of traffic handling or even inject malicious behavior.
No active exploitation of these six new bugs has been reported so far, though one related APM zero-day (CVE-2026-94127) was confirmed exploited earlier. That earlier flaw underscores how dangerous misconfigurations or overlooked setups can leave systems exposed. With engineering hotfixes delivered today, these revelations serve as call to action for affected organizations.
What to do now: Audit all BIG-IP deployments for iRules usage and HTTP, DNS, or agent settings matching the risky use cases. Prioritize hotfix installations, especially on instances positioned at exposed network edges like internet-facing virtual servers. Since there are no workarounds listed for the critical flaws, patching promptly will be the only way to avoid potential attacks.
In short: F5’s latest findings reinforce a growing reality — edge devices, where traffic and security intersect, are prime targets. Administrators must assume flaws exist until proven otherwise, keep configurations tight, and make patching a routine priority. What to watch next: whether attackers begin exploiting one or more of these bugs now that hotfixes are public, and how resilient F5’s next major releases will be in hardening iRules and policy logic against buffer overflow risks.