Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.3
CVE-2026-120292: F5 BIG-IP can crash or be taken over via crafted web requests
CVE-2026-120292 · published 3 days ago
Summary
If you use an HTTP profile together with an iRule that includes the MR::message route command on an F5 BIG-IP or BIG-IP Next for Kubernetes device, a specially crafted request can stop the traffic‑handling engine and potentially let an attacker run code on the system. This can cause service interruptions and possibly full system compromise. Update to the latest patches or remove the vulnerable iRule configuration to protect your environment.
What to do
- Update f5 big-ip to version BIGIP-21.1.0.4.0.19.3-ENG.
- Update f5 big-ip next for kubernetes to version BNK-2.4.2-EHF1.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| f5 | big-ip |
< * Fix: upgrade to BIGIP-21.1.0.4.0.19.3-ENG
|
| f5 | big-ip next for kubernetes |
< * Fix: upgrade to BNK-2.4.2-EHF1
|
Original advisory text
BIG-IP iRule vulnerability
Description:
When an HTTP profile and an iRule using the
MR::message
route command are 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.
When an HTTP profile and an iRule using the
MR::message
route command are 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.
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Severity
9.3
Critical
Type
CWE-121Stack-based Buffer Overflow
Timeline
Published18 Nov 2026
Updated21 Nov 2026
First seen18 Nov 2026
Track software like this
Free during beta