F5 ships out-of-band hotfixes for six critical BIG-IP RCE flaws
F5 released out-of-band hotfixes for six unauthenticated CVSS 9.8 buffer-overflow RCE flaws in BIG-IP, plus an iControl REST token issue. Data plane only, no known exploitation.
F5 released out-of-band engineering hotfixes this week for six critical stack-based buffer overflows in BIG-IP, each scored CVSS 9.8 and each exploitable by an unauthenticated remote attacker to crash the Traffic Management Microkernel (TMM) and potentially execute code. A seventh advisory covers an iControl REST token-handling issue. None are flagged as exploited, and F5 says the management plane is not exposed — this is a data-plane problem. The advisories went up on November 18–19; the fixes are hotfixes, not standard releases.
The flaws
All six overflows carry CVSS 9.8. Per F5's advisories, each is reachable in a specific data-plane configuration:
- CVE-2026-123637 — BIG-IP APM, when a per-request policy includes the Client Information and Endpoint Security agents (K000163937).
- CVE-2026-121805 — BIG-IP PEM, BIG-IP Next for Kubernetes, and CNF, via an iRule using
PEM::subscriber(K000163946). - CVE-2026-120292 — BIG-IP (all modules) and Next for Kubernetes, via an HTTP profile plus an iRule using
MR::message route(K000163940). - CVE-2026-120285 — BIG-IP (all modules), Next for Kubernetes, and CNF (K000163939).
- CVE-2026-116953 — BIG-IP (all modules) and Next for Kubernetes, via an iRule using
GENERICMESSAGE::route(K000163941). - CVE-2026-120722 — BIG-IP DNS and Next for Kubernetes, via an iRule using
DNS::scrape.
Secondary reporting still disagrees on whether BIG-IP CNF is affected for a couple of these: F5's advisory text lists CNF as not vulnerable in places, while the CVE records updated this week list CNF as affected. Confirm against the per-CVE advisory for your exact module set.
What's affected
F5 lists the affected BIG-IP branches as 21.1.0, 17.5.0–17.5.1, and 17.1.0–17.1.3. Because F5 only evaluates versions still under technical support, older releases absent from the tables have not been shown to be safe. For the six overflows, F5 is shipping engineering hotfixes rather than standard maintenance releases; BIG-IP Next for Kubernetes and CNF have dedicated EHF builds (e.g. BNK-2.4.2-EHF1, CNF-2.4.2-EHF1).
Exploitation status
F5's advisories do not report any of these as exploited, and no attacker is named. For scale: Shadowserver tracks more than 177,000 internet-exposed BIG-IP instances. Context worth weighing — in September, F5 patched CVE-2026-94127, a critical BIG-IP APM flaw that was exploited as a zero-day, so BIG-IP's data plane is a live target even when a given batch isn't yet.
Action checklist
- Inventory which of the six configurations you actually run — APM per-request policies, PEM, DNS, and the specific iRule commands (
PEM::subscriber,MR::message route,GENERICMESSAGE::route,DNS::scrape). That tells you which CVEs apply. - Apply the F5 engineering hotfixes for the modules you run. There are no F5-listed mitigations for the overflows.
- For Next for Kubernetes and CNF, move to the EHF builds.
- Restrict data-plane exposure where you can while scheduling the hotfixes — these are unauthenticated and pre-auth.
- Review F5's September APM advisory (CVE-2026-94127) if you haven't already; that one was exploited in the wild.
Context
A batch of six unauthenticated 9.8s in a load balancer that sits in front of the application is the kind of disclosure that draws reverse-engineers fast, even without a PoC. The saving grace is configuration specificity: unlike a blanket pre-auth RCE, each bug needs a particular module and iRule in play. Map your config to the list, hotfix what matches, and don't wait for a working exploit to make the decision for you.