F5 releases emergency patches for critical BIG-IP RCE flawsNew
Five critical buffer overflows in BIG-IP APM and iRules allow unauthenticated remote code execution, and F5 offers no mitigations.
DoS and possible RCE in F5 BIG-IP via GENERICMESSAGE::route iRule
A flaw in F5 BIG-IP's Traffic Management Microkernel can be triggered when a virtual server runs an iRule that processes client traffic with GENERICMESSAGE::route. A remote, unauthenticated attacker can send undisclosed requests that terminate TMM, disrupting traffic until it restarts, and may gain remote code execution. This is a data-plane issue only; the control plane is not exposed. Only systems using that iRule configuration are affected.
What to do: Apply F5's update for CVE-2026-116953. No workaround is stated.
| Product | Affected |
|---|---|
| F5 BIG-IP | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description: When an iRule that processes client traffic using the GENERICMESSAGE::route command is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE). Impact: Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may allow the attacker to perform RCE. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Five critical buffer overflows in BIG-IP APM and iRules allow unauthenticated remote code execution, and F5 offers no mitigations.
Each flaw needs a specific iRule or APM setup; F5 offers only engineering hotfixes and lists no workaround.
Named engineering hotfixes cover BIG-IP 17.1, 17.5 and 21.1, plus CNF, Next for Kubernetes and BIG-IQ.
Today 952 readers · 1.1K views · 90 reads · all time 211K views