F5 discloses six critical BIG-IP flaws that can crash traffic
Each flaw needs a specific iRule or APM setup; F5 offers only engineering hotfixes and lists no workaround.
Stack buffer overflow in F5 BIG-IP TMM via DNS::scrape iRule
On F5 BIG-IP, undisclosed client requests can terminate the Traffic Management Microkernel when a virtual server uses an iRule that calls DNS::scrape. A remote, unauthenticated attacker on the data plane can disrupt traffic until TMM restarts and may also run code. There is no control-plane exposure. Only systems with that iRule are affected; affected builds are not listed.
What to do: Apply F5's update for CVE-2026-120722. No workaround is stated; remove or avoid DNS::scrape iRules only if operations allow.
| 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 DNS::scrape 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. In addition, the attacker may be able 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.
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