F5 BIG-IP Vulnerability: Critical No-Login Flaws in APM and iRules Can Crash TMM, No Workaround, and the Emergency Hotfixes to Install
F5 shipped emergency hotfixes for critical BIG-IP APM and iRules flaws that let attackers with no login crash TMM and disrupt traffic. There is no workaround. Here is what is confirmed and what to install.
Where Worldwide
On this page 9 sections
F5 has released emergency hotfixes for a group of critical flaws in BIG-IP, its equipment for managing network traffic and access. An attacker with no login can use these flaws to crash the part of BIG-IP that moves your traffic. If you run BIG-IP Access Policy Manager (APM) or use iRules, plan to install the hotfix this week.
F5 has not flagged any of the flaws as exploited in attacks. The reporting also says there is no workaround you can switch on while you wait. Below is what is confirmed, what is still not known, and a checklist for this week.
What happened with the F5 BIG-IP vulnerabilities
BleepingComputer's report is dated Friday, November 20, 2026. It says F5 released out-of-band hotfixes on Wednesday for critical flaws in BIG-IP Access Policy Manager (APM), which the report calls the company's centralized access management proxy solution, and in BIG-IP iRules. It lists five CVE IDs:
- CVE-2026-121805
- CVE-2026-120292
- CVE-2026-120285
- CVE-2026-116953
- CVE-2026-123637
BleepingComputer says all five are rated critical severity. The Hacker News counts six flaws, adding CVE-2026-120722. It reports that F5 rates all six 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0. Neither report we checked explains why one counts five and the other six. If you track this by CVE, track all six.
According to The Hacker News, WatchTowr researcher Sina Kheirkhah reported four of the flaws, and F5 found the other two itself.
What attackers can do: crash TMM, not reach the management side
Here is the confirmed impact. Attackers with no login can exploit the flaws to terminate the Traffic Management Microkernel (TMM), the BIG-IP process that handles the traffic passing through the device. The description quoted in BleepingComputer's report is direct about the result: "Traffic is disrupted while the TMM process restarts."
The same description limits the scope: "There is no control plane exposure; this is a data plane issue only." In plain terms, these flaws do not expose the side of the device you use to manage it. The risk is that the traffic itself stops.
Some coverage, including the address of BleepingComputer's report, calls these RCE (remote code execution) flaws. The only impact the reports we checked describe in detail is TMM being terminated. Those reports do not say whether any of the flaws let an attacker run code on the device, so we are not claiming that.
Is the F5 BIG-IP flaw being exploited?
No exploitation has been confirmed. F5 has not flagged any of the issues as exploited in attacks.
The product is everywhere, though. The internet monitoring group Shadowserver currently tracks more than 177,000 BIG-IP instances, and F5 serves more than 23,000 customers, including 80% of the Fortune Global 500. The 177,000 figure is not a count of vulnerable devices. Nobody has said how many of those instances run APM or iRules.
Is there an F5 BIG-IP workaround? No
The Hacker News reports that there are no mitigations for these flaws, so the fix is the engineering hotfix. It also flags a trade-off: engineering hotfixes do not undergo the extensive QA assessment that scheduled software releases get.
That is not a reason to wait. Without a workaround, the hotfix is the only fix. Test it where you can and have a way to roll it back.
F5 BIG-IP fixed versions and hotfixes
| Product | What to install | Notes |
|---|---|---|
| BIG-IP Next for Kubernetes | BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 or BNK-2.2.5-EHF1, whichever matches the release line you run | Versions as reported by The Hacker News |
| BIG-IP CNF | CNF-2.4.2-EHF1, CNF-2.3.4-EHF1 or CNF-2.2.5-EHF1, whichever matches the release line you run | Versions as reported by The Hacker News |
| BIG-IP APM and BIG-IP iRules | The out-of-band hotfix for your BIG-IP version | The reports we checked do not list the exact hotfix builds. Get them from F5's security advisory for each CVE above |
What to do this week
- List every BIG-IP you have. Include BIG-IP Next for Kubernetes and CNF deployments, plus any BIG-IP run for you by a hosting provider or managed service. Write down who is responsible for patching each one.
- Find out which ones use APM or iRules. APM is the access proxy. If staff or customers log in through BIG-IP, that device is a priority.
- Match each device to its hotfix. Look up each CVE in F5's advisory and find the hotfix for the exact version on that device. For Kubernetes and CNF, use the EHF1 builds in the table above.
- Back up the configuration first. Hotfixes get less testing than scheduled releases, so make sure you can roll back.
- Test before production if you can. If you have a standby or lab unit, patch it first and check that your websites, apps and remote access logins still work.
- Book a maintenance window and tell people. Let staff and any affected customers know when traffic through the device may be interrupted.
- Confirm afterwards. Check that the hotfix shows as installed on every device on your list, not just the main one.
- Watch for crashes until every device is patched. Treat any unexplained TMM restart or sudden traffic drop on an unpatched device as something to look into.
Why it matters for a business network or website
In a business that uses BIG-IP, the device usually sits in front of the things customers and staff depend on: the website, the customer portal, internal apps and remote access logins. These flaws do not expose the management side, but crashing TMM disrupts that traffic. If someone can trigger the crash without logging in, your website and remote access can go down with no warning, and they may go down again after TMM comes back.
This is the same kind of risk we covered in the Cisco ASA DNS flaw that could reboot firewalls: the attacker does not need to break in to do damage, because knocking the gateway over is enough.
The less-tested hotfix raises a second question: who in your business decides when an emergency fix goes in, and who tests it? If the answer is unclear, read who is patching the software that runs your business. Also make sure every device has actually been patched, not just updated somewhere. We covered that gap in updated is not the same as patched.
F5 BIG-IP vulnerability questions people are asking
Which F5 BIG-IP products are affected?
The reports name BIG-IP Access Policy Manager (APM) and BIG-IP iRules. Fixed builds are also listed for BIG-IP Next for Kubernetes and BIG-IP CNF. To see exactly which versions and modules are affected, check F5's advisory.
What are the CVE numbers for the F5 BIG-IP flaws?
They are CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953 and CVE-2026-123637. The Hacker News adds a sixth, CVE-2026-120722.
How severe are they?
They are rated critical. The Hacker News reports that F5 rates all six 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0.
Is this an F5 RCE vulnerability?
It is described that way in some coverage. The confirmed impact is that attackers with no login can terminate TMM, which disrupts traffic. The reports we checked do not say whether code execution is possible.
Is it being exploited?
Not as far as anyone has confirmed. F5 has not flagged any of the flaws as exploited in attacks.
Is there a workaround or mitigation?
No. The reporting says there are no mitigations. Install the hotfix.
Does it expose the BIG-IP management interface?
No. The quoted description says there is no control plane exposure, only the data plane.
Who found the flaws?
WatchTowr researcher Sina Kheirkhah reported four, and F5 found the other two itself.
Is the emergency hotfix safe to install?
It is the only fix available. Engineering hotfixes get less QA than scheduled releases, so back up your configuration, test on a standby unit if you have one, and install it this week.
The bigger lesson
The device that carries all your traffic is also a single point of failure. When a no-login crash bug lands with no workaround and only a lightly tested hotfix, how fast you recover depends on whether you already know what you run, who patches it, and how you roll back. Write those three answers down before the next advisory comes out.
Want your gateways and servers reviewed and kept patched? See security hardening or get a quote.
Get security alerts like this by email, plus the free checklist, at security alerts.
Sources: BleepingComputer: F5 releases emergency patches for critical BIG-IP flaws; The Hacker News: F5 warns of 6 critical BIG-IP flaws.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Linux KVM Vulnerability CVE-2026-99312: AMD Hosts With Nested Virtualization Affected, What Is Confirmed and How to Check Yours
A Linux kernel flaw in the KVM hypervisor, CVE-2026-99312, affects hosts with AMD processors and nested virtua...
PHP Critical Vulnerability: Seven RCE Flaws Fixed in PHP 8.5.13 and 8.6.0, Which Version to Install for Your Branch and Who Is Exposed
PHP's 19 November 2026 security releases fix seven critical remote code execution flaws. Here is which version...
PHP Session Vulnerability: CVE-2026-126714 and CVE-2026-115560 Can Lead to Remote Code Execution, Fixed in PHP 8.5.13, and What to Check This Week
PHP has fixed two session flaws, CVE-2026-126714 and CVE-2026-115560, that can lead to remote code execution....