← All articles

BIG-IP flaws threaten traffic uptime in specific setups

BIG-IP flaws threaten traffic uptime in specific setups

BIG-IP administrators face six critical vulnerabilities that can crash the platform’s Traffic Management Microkernel, or TMM, the component that processes almost all network traffic. An attacker does not need to log in, but each flaw requires a particular configuration on a virtual server, a software-defined service endpoint. A successful attack can disrupt traffic until TMM restarts, and F5 says the flaws may also allow remote code execution, meaning an attacker could run commands on the affected system.

F5 rates all six vulnerabilities 9.8 under CVSS version 3.1 and 9.3 under CVSS version 4.0. CVSS is a scoring system used to describe the severity of security flaws. The vulnerabilities are stack-based buffer overflows, memory-handling errors that can overwrite data in a program’s call stack. F5 says the management side of BIG-IP is not exposed to these flaws because they affect the data plane, the part that handles network traffic.

F5’s advisories do not say that any of the six flaws have been exploited. WatchTowr reported four of them, while F5 discovered the other two. Five affect iRules, a BIG-IP feature that administrators use to control traffic, and one affects the BIG-IP Access Policy Manager, or APM, module.

The required configurations are specific. CVE-2026-123637 affects BIG-IP APM when an APM per-request policy contains both the Client Information agent and Endpoint Security agents. CVE-2026-121805 affects BIG-IP PEM, BIG-IP Next for Kubernetes and, as of the advisory, BIG-IP CNF when an iRule uses PEM::subscriber on client traffic. CVE-2026-120292 requires an HTTP profile and an iRule using MR::message route, and affects all BIG-IP modules and BIG-IP Next for Kubernetes.

CVE-2026-120285 requires an HTTP profile and an iRule using PSC::ip_address. It affects all BIG-IP modules, BIG-IP Next for Kubernetes and BIG-IP CNF. CVE-2026-116953 requires an iRule using GENERICMESSAGE::route on client traffic and affects all BIG-IP modules and BIG-IP Next for Kubernetes. CVE-2026-120722 requires an iRule using DNS::scrape on client traffic and affects BIG-IP DNS and BIG-IP Next for Kubernetes. F5’s advisory says BIG-IP CNF is not vulnerable to that flaw, but the CVE record updated the same day lists CNF as affected, leaving that point inconsistent.

For these six critical issues, F5 lists engineering hotfixes as the only fixes. These are builds issued between normal software releases. The advisories list no scheduled release as a fix and provide no workaround before a hotfix is installed. F5 warns that engineering hotfixes do not receive the extensive quality assurance assessment used for scheduled releases, and its hotfix policy says they come without a warranty or promise that they will work. Systems running a custom engineering hotfix require a new hotfix from F5’s support team.

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 to 2.4.2, 2.3.0 to 2.3.4 and 2.2.0 to 2.2.5. For CVE-2026-121805 and CVE-2026-120285, BIG-IP CNF is fixed in CNF-2.4.2-EHF1, CNF-2.3.4-EHF1 and CNF-2.2.5-EHF1 across the same version ranges. F5 checks only versions still within technical support, so an older release absent from its tables has not been shown to be safe.

F5’s security notification also lists 22 advisories published at the same time, including 10 for NGINX. Six additional, lower-rated flaws affect BIG-IP and BIG-IQ. CVE-2026-125274, rated 8.8, affects iControl SOAP. A user with network access and at least the Guest role can send an unauthorised management request that may allow system commands, file creation or deletion, or service disruption. It is fixed in BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6, and BIG-IQ 8.4.2.3. Until then, F5 describes how to limit iControl SOAP to trusted networks, while warning that blocking it on self-IP addresses can affect high-availability setups.

CVE-2026-120718, rated 8.1, affects iControl REST because tokens may remain valid longer than expected. Someone who already has a token may be able to extend its validity unless the token owner deletes it. Fixes are in BIG-IP 21.1.0.2, 17.5.1.10 and 17.1.3.6. F5 recommends changing token-creating scripts to delete tokens when they are no longer needed.

Four further flaws are rated 7.5. CVE-2026-125272 can crash TMM without login when an APM access profile has a per-request policy with a form-based Logon Page. CVE-2026-126822 can crash TMM when an access profile is configured as a SAML Service Provider, or SP, a system that provides login services to another application. Until it is fixed, F5 suggests removing the SAML Auth agent if SAML SP is unnecessary and restricting that virtual server to trusted client networks. Both are fixed in the same engineering hotfixes as the six critical flaws.

CVE-2026-126336 can crash TMM when a SAML SP agent uses encrypted assertions. It is fixed in BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6, and F5 recommends high availability to reduce the impact. CVE-2026-121812 affects APM and SSL Orchestrator when a per-request policy enables the tmm.access.policytrace database key, which is off by default. APM is fixed in the same engineering hotfixes, while SSL Orchestrator fixes are listed only on the 21.1 and 17.1 branches.

These flaws are separate from CVE-2026-94127, an APM vulnerability disclosed by F5 on September 22 and later exploited. CISA, the U.S. Cybersecurity and Infrastructure Security Agency, added it to the Known Exploited Vulnerabilities catalogue the same day. That issue was a heap-based buffer overflow in APM configurations operating as OAuth authorisation servers and allowed unauthorised code execution. The six critical flaws discussed here are stack-based overflows that require different settings. For organisations running affected BIG-IP services, AEU-I provides security-first IT, infrastructure and consulting that can be relevant when planning the review and remediation of these systems.

Also available in: DeutschItalianoShqip