CVE-2026-116953 is a critical data-plane vulnerability in F5 BIG-IP and BIG-IP Next for Kubernetes: requests sent to a virtual server whose iRule uses GENERICMESSAGE::route can crash the Traffic Management Microkernel (TMM) and may lead to remote code execution.
What Is It
The flaw affects virtual servers configured with an iRule that uses the GENERICMESSAGE::route command to process client traffic. On those servers, undisclosed requests can make TMM terminate and may lead to remote code execution (RCE). F5 classifies the weakness as CWE-121 (stack-based buffer overflow).
F5 SIRT published the record on 2026-11-18. NVD lists its status as "Received."
Why It Matters
- Severity: CVSS 3.1 base score 9.8 (CRITICAL), vector
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The CVSS 4.0 score is 9.3 (CRITICAL). - Attacker requirements: The attacker can be remote and needs no authentication or user interaction.
- Impact: Traffic stops while TMM restarts, which is a denial-of-service. The attacker may also be able to run code.
- Scope: F5 says there is no control-plane exposure. This is a data-plane issue only.
- Exploitation status: This CVE is not in the CISA KEV catalog, so active exploitation has not been confirmed. CISA's SSVC assessment rates exploitation "none," automatable "yes," and technical impact "total."
What's Vulnerable
Only configurations that use the GENERICMESSAGE::route iRule command on a virtual server are affected.
F5 BIG-IP:
- 21.1.0 branch: unaffected starting at BIGIP-21.1.0.4.0.19.3-ENG
- 17.5.0 branch: unaffected at BIGIP-17.5.1.10.0.80.35-ENG and BIGIP-17.5.1.11.0.61.12-ENG
- 17.1.0 branch: unaffected at BIGIP-17.1.3.6.0.14.20-ENG and BIGIP-17.1.3.7.0.21.4-ENG
F5 BIG-IP Next for Kubernetes:
- 2.4.0 branch: unaffected at BNK-2.4.2-EHF1
- 2.3.0 branch: unaffected at BNK-2.3.4-EHF1
- 2.2.0 branch: unaffected at BNK-2.2.5-EHF1
F5 did not evaluate software versions that have reached End of Technical Support (EoTS).
Patch Status
F5 lists the engineering builds above as unaffected for each supported branch. There is no KEV entry, so CISA has not set a required action or due date.
Administrators should:
1. Find virtual servers whose iRules call GENERICMESSAGE::route.
2. Check F5 advisory K000163941 for the fixed builds and guidance that apply to their branch.
3. Prioritize internet-facing BIG-IP data-plane instances, because the flaw needs no authentication and is rated automatable.
If you run an EoTS release, F5 did not assess it, so don't assume it is safe.