Description: When an HTTP profile and an iRule using the MR::message route command are configured on a virtual server
Source GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 18 Nov 2026, 20:23 UTC
Thin evidence
One scorer or none| CNA (f5) | CVSS 3.1 | 9.8 |
|---|---|---|
| CNA (f5) | CVSS 4.0 | 9.3 |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| F5BIG-IP | Affected
| Fixed in– |
| F5BIG-IP Next for Kubernetes | Affected
| Fixed in– |
AI-suggested
In the meantime, consider avoiding configurations that combine HTTP profiles with iRules using the MR::message route command if feasible.
Description
A vulnerability exists in BIG-IP systems when an HTTP profile and an iRule using the MR::message route command are configured on a virtual server. This flaw can cause the Traffic Management Microkernel (TMM) to terminate unexpectedly, leading to traffic disruption and potential remote code execution by a remote, unauthenticated attacker. The issue affects the data plane only and does not expose the control plane. Versions that have reached End of Technical Support are not evaluated.