F5 Rushes Hotfixes for Six Critical BIG-IP Flaws: Patch Now
F5 has released emergency engineering hotfixes for six critical BIG-IP flaws that can crash traffic and may allow remote code execution without a login. Here is who is exposed and what to do.
In this article
F5 BIG-IP devices sit at the front door of many bank, telecom, government and enterprise networks, handling application traffic, load balancing and remote access. On 18 November 2026 F5 released out-of-band engineering hotfixes for a set of critical BIG-IP vulnerabilities that an attacker can trigger without logging in. This briefing is for IT and security teams, and for business leaders whose managed service providers run F5 gear on their behalf.
Key takeaways
- F5 disclosed six critical stack-based buffer overflows in BIG-IP, each rated 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0.
- Unauthenticated attackers can crash the Traffic Management Microkernel (TMM), interrupting traffic, and F5 says the flaws may also allow remote code execution.
- Each flaw only applies to a specific configuration, mostly certain iRule commands or a particular APM policy setup.
- The only fixes are engineering hotfixes; F5 lists no workaround.
- No exploitation has been reported yet, but F5 products are a frequent target.

What happened
F5 published 22 security advisories in one day, including 10 for NGINX, The Hacker News reports. The most serious are six flaws in BIG-IP’s data plane, the part of the system that processes nearly all network traffic. F5 says the management side (control plane) is not exposed by these bugs.
When triggered, each flaw causes TMM to terminate. Traffic through the device is disrupted until TMM restarts, and F5 warns that remote code execution may also be possible. Four of the six were reported by watchTowr researcher Sina Kheirkhah; F5 found the other two itself.
BleepingComputer’s first report counted five critical flaws plus a high-severity APM SAML bug; F5’s full advisory set, as summarised by The Hacker News, lists six critical issues and several lower-rated ones.
Which setups are vulnerable
These are not “every BIG-IP is exposed” bugs. Each one needs a specific setup on a virtual server:
- CVE-2026-123637: an APM per-request policy that includes both the Client Information agent and Endpoint Security agents (BIG-IP APM only).
- CVE-2026-121805: an iRule that uses PEM::subscriber on client traffic.
- CVE-2026-120292: an HTTP profile plus an iRule using MR::message route.
- CVE-2026-120285: an HTTP profile plus an iRule using PSC::ip_address.
- CVE-2026-116953: an iRule using GENERICMESSAGE::route on client traffic.
- CVE-2026-120722: an iRule using DNS::scrape on client traffic (BIG-IP DNS).
Some of these also affect BIG-IP Next for Kubernetes and BIG-IP CNF, part of F5’s cloud-native edition.
Other fixes in the same batch
F5 also fixed lower-rated BIG-IP and BIG-IQ issues. They include an iControl SOAP flaw (CVE-2026-125274, rated 8.8) that could let a user with only the Guest role send unauthorised management requests, an iControl REST token expiry problem, and several APM and SAML bugs that let attackers crash TMM. Some of these are fixed in regular releases (BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6), others in the same engineering hotfixes.
Why it matters
Internet watchdog Shadowserver tracks more than 177,000 BIG-IP instances exposed online, and over 14,600 IP addresses showing BIG-IP APM fingerprints, according to BleepingComputer. It is not known how many are vulnerable configurations or already patched.
History is the bigger warning. CISA has flagged at least seven F5 vulnerabilities as actively exploited since November 2021, four of them used by ransomware gangs. In September 2026 F5 patched a different critical APM flaw (CVE-2026-94127) that was exploited as a zero-day. Crashing a BIG-IP can take customer-facing services offline, and code execution on a device at the network edge is a valuable foothold.
A caution about hotfixes
F5 notes that engineering hotfixes do not go through the full QA testing of scheduled releases and come with no warranty. Systems already running a custom engineering hotfix need a new one from F5 support. F5 also checks only versions still under technical support, so an older release missing from its tables should not be assumed safe.
What you should do
- Inventory: list every BIG-IP, BIG-IP Next for Kubernetes and CNF instance you run, including ones managed by a partner or hosting provider.
- Check configurations: search your iRules for the commands listed above, and review APM per-request policies for the Client Information plus Endpoint Security agent combination.
- Apply hotfixes: install the relevant engineering hotfixes from F5, starting with internet-facing devices. Use a maintenance window and keep a rollback plan, since hotfixes get less testing.
- Restrict management access: keep iControl SOAP and REST interfaces reachable only from trusted admin networks, as F5 advises.
- Watch for crashes: unexpected TMM restarts could indicate exploitation attempts. Alert on them and keep logs.
- Ask your providers: if a bank, telco or MSP runs F5 gear for you, ask them to confirm in writing that these advisories have been assessed and patched.
Sources
- BleepingComputer: F5 releases emergency patches for critical BIG-IP RCE flaws
- The Hacker News: F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE
Featured image: Photo: “F5 spokane 2” by אלון כהן – Alon Cohen, CC BY-SA 4.0, via Wikimedia Commons — source
Was this article helpful?
adminVerified expert
Cybersecurity Analyst
Federal Capital Territory (Abuja)
Credentials: MCPN, MNCS, IAENG | System Analyst · Web Developer · CEH · CC · CDST
Got expertise to share? Write for us →


