F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE
Six critical vulnerabilities in F5 BIG-IP allow an attacker to crash the Traffic Management Microkernel (TMM) without logging in, disrupting traffic until the TMM restarts.

Six critical vulnerabilities in F5 BIG-IP allow an attacker to crash the Traffic Management Microkernel (TMM) without logging in, disrupting traffic until the TMM restarts.
Each flaw needs a specific setup on a virtual server: an iRule that uses a particular command, or an APM policy that includes two particular kinds of agent.
F5, which makes BIG-IP, disclosed the flaws today and says they may also allow remote code execution.
None of the company's advisories says the flaws have been exploited; watchTowr researcher Sina Kheirkhah reported four, and the company found the other two itself.
A system on a custom engineering hotfix needs a new one from the company'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.
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.
The company checks only versions that are still within technical support, so an older release missing from its tables has not been shown to be safe.
Today's flaws differ from CVE-2026-94127, an APM flaw that F5 disclosed on September 22 and that was later exploited.
For the six critical flaws, the only fixes are engineering hotfixes, builds that the company issues between its normal software releases, and no scheduled release is listed as a fix, and the advisories provide no workaround until a hotfix is installed.
Why it matters
That flaw is a heap-based buffer overflow in APM setups that serve as OAuth authorization servers, allowing attackers to run code without logging in.