F5 BIG-IP Buffer Overflow Flaws: Six Critical CVEs, Who Is Affected and How to Patch
F5 disclosed six critical BIG-IP stack buffer overflows (CVSS 9.8) that crash TMM without login. Affected versions, risky configs and hotfixes.
Table of contents
F5 has disclosed six critical stack-based buffer overflow vulnerabilities in BIG-IP, its widely used application delivery and load-balancing platform. All six were published on November 18, 2026, and each is rated 9.8 on CVSS v3.1 (9.3 on CVSS v4.0), according to F5's advisories as summarised by H-ISAC.
The flaws let an attacker who has not logged in crash the Traffic Management Microkernel (TMM), the process that handles all traffic passing through a BIG-IP. F5 says memory corruption may also lead to remote code execution. The only fixes are engineering hotfixes, and F5 lists no workaround.
If your organisation runs BIG-IP, BIG-IP Next for Kubernetes or BIG-IP CNF, here is what is confirmed and what to do.
What happened
Each of the six advisories describes the same kind of bug in a different feature. Crafted requests, which F5 has not described publicly, overflow a buffer on TMM's stack. TMM terminates, and traffic through the device stops until the process restarts. Because BIG-IP usually sits in front of business applications, a crash can take those applications offline.
F5 states that these are data plane issues only: the management interface (control plane) is not exposed. The Hacker News report notes that watchTowr researcher Sina Kheirkhah reported four of the flaws and F5 found the other two internally.
The six critical CVEs
A system is only exposed if it uses the specific configuration each advisory names:
| CVE | Vulnerable configuration | Products |
|---|---|---|
| CVE-2026-123637 | APM per-request policy that includes both the Client Information and Endpoint Security agents | BIG-IP APM |
| CVE-2026-116953 | iRule using GENERICMESSAGE::route on client traffic |
BIG-IP (all modules), BIG-IP Next for Kubernetes |
| CVE-2026-120285 | HTTP profile plus an iRule using PSC::ip_address |
BIG-IP (all modules), Next for Kubernetes, CNF |
| CVE-2026-120292 | HTTP profile plus an iRule using MR::message route |
BIG-IP (all modules), Next for Kubernetes |
| CVE-2026-121805 | iRule using PEM::subscriber on client traffic |
BIG-IP PEM, Next for Kubernetes, CNF |
| CVE-2026-120722 | iRule using DNS::scrape on client traffic |
BIG-IP DNS, Next for Kubernetes |
F5 revised several advisories on November 19 to add BIG-IP CNF as affected, so check the current version of each advisory rather than relying on early reports.
Affected versions and fixes
According to the Canadian Centre for Cyber Security's summary of F5's advisories, these builds are affected and these hotfixes fix them:
| Product | Affected | Install |
|---|---|---|
| BIG-IP 17.1.x | 17.1.0–17.1.3 without the hotfix | BIGIP-17.1.3.7.0.21.4-ENG |
| BIG-IP 17.5.x | 17.5.0–17.5.1 without the hotfix | BIGIP-17.5.1.11.0.61.12-ENG |
| BIG-IP 21.1.x | 21.1.0 without the hotfix | BIGIP-21.1.0.4.0.19.3-ENG |
| BIG-IP Next for Kubernetes | 2.2.0–2.4.x | BNK-2.2.5-EHF1, BNK-2.3.4-EHF1 or BNK-2.4.2-EHF1 |
| BIG-IP CNF | 2.2.0–2.4.x | CNF-2.2.5-EHF1, CNF-2.3.4-EHF1 or CNF-2.4.2-EHF1 |
Two caveats matter. First, F5 warns that engineering hotfixes do not go through the full QA of scheduled releases, so test them before rolling out widely. Second, F5 only evaluates versions still under technical support; an older release missing from the tables is not confirmed safe. If you already run a custom hotfix, F5 support must build you a new one.
Is it being exploited?
As of this writing, none of the six advisories reports exploitation in the wild. That is not a reason to wait. BIG-IP is a frequent target: in September 2026, F5 disclosed a different APM heap-based overflow, CVE-2026-94127, which Rapid7 describes as an unauthenticated remote code execution flaw, and which was exploited and added to CISA's Known Exploited Vulnerabilities catalog. Once technical details or patch diffs circulate, attackers often move fast.
What to do now
- Inventory. List every BIG-IP, BIG-IP Next for Kubernetes and CNF instance and its exact version.
- Check configurations. Search your iRules for
GENERICMESSAGE::route,PSC::ip_address,MR::message route,PEM::subscriberandDNS::scrape, and review APM per-request policies for the Client Information plus Endpoint Security agent combination. - Patch exposed systems first. Prioritise internet-facing virtual servers that match a vulnerable configuration. Test the engineering hotfix in staging, then deploy.
- Reduce impact while you patch. If an iRule command is not essential, consider removing it from client-facing virtual servers until the hotfix is installed. A high-availability pair limits downtime if TMM crashes.
- Watch for crashes. Unexpected TMM restarts after November 18 are worth investigating as possible exploitation attempts.
F5 also published six lower-rated BIG-IP and BIG-IQ fixes at the same time, including TMM crash bugs in APM's SAML and logon-page features. Many are fixed by the same hotfixes, so one maintenance window can cover most of them.
For more on recent critical server-side flaws, see our coverage of the VMware vCenter zero-day and the Java OpenJDK flaw.
Frequently asked questions
+Are the F5 BIG-IP buffer overflow flaws being exploited?
As of November 21, 2026, none of F5's six advisories reports exploitation in the wild. That can change quickly, and a separate BIG-IP APM overflow disclosed in September 2026 (CVE-2026-94127) was exploited, so treat these as urgent.
+Does an attacker need to log in?
No. All six flaws can be triggered by an unauthenticated attacker sending crafted traffic to an affected virtual server. The management interface (control plane) is not exposed.
+Is every BIG-IP system vulnerable?
No. A system must run an affected version and use a specific configuration, such as an iRule that calls GENERICMESSAGE::route, PSC::ip_address, MR::message route, PEM::subscriber or DNS::scrape, or an APM per-request policy with both the Client Information and Endpoint Security agents.
+How do I fix the F5 BIG-IP buffer overflows?
Install the November 18 engineering hotfix for your branch: BIGIP-17.1.3.7.0.21.4-ENG, BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-21.1.0.4.0.19.3-ENG. BIG-IP Next for Kubernetes and BIG-IP CNF have their own EHF1 hotfixes. F5 lists no workaround.
Sources & references
- Canadian Centre for Cyber Security — F5 security advisory (AV26-1178), Nov 19, 2026
- F5 — K000163937: BIG-IP APM vulnerability CVE-2026-123637
- F5 — K000163941: BIG-IP iRule vulnerability CVE-2026-116953
- H-ISAC — Six Critical F5 BIG-IP Flaws Could Lead to RCE (Nov 19, 2026)
- The Hacker News — F5 warns six critical BIG-IP flaws can crash TMM (Nov 2026)
- Rapid7 — CVE-2026-94127: Critical Unauthenticated RCE in F5 BIG-IP APM (Sep 2026)
Spotted an error? See our Corrections Policy.
- #f5
- #big-ip
- #cve
- #buffer-overflow
- #vulnerability
- #irules
- #apm
The KernelBrief editorial desk researches, writes and fact-checks every article published on this site. Every article is checked against primary sources (official documentation, vendor announcements, standards bodies and original research) before publication. Every factual claim is linked to its source, and corrections are handled under our published Corrections Policy.
Related articles
VMware vCenter Zero-Day CVE-2026-123890 Was Exploited for Months: Who Is Affected and How to Patch
VMSA-2026-0009 fixes vCenter auth bypass CVE-2026-123890, exploited since September per Mandiant. Fixed builds, no workaround, and what to check.
· 6 min read
Java4Shell (CVE-2026-114938): The OpenJDK Base64 Bug Explained, Who Is Affected and How to Patch
Java4Shell is a critical OpenJDK Base64 decoder bug on AVX-512 x86-64 CPUs. Affected Java versions, fixed builds, the JVM flag workaround and how to check.
· 6 min read
LiteLLM Flaw CVE-2026-40217 Is Being Exploited in LLMjacking Attacks: Who Is Affected and How to Patch
CISA added LiteLLM flaw CVE-2026-40217 to its exploited list. Affected versions, why it matters for LLMjacking, and how to patch and rotate keys.
· 7 min read