NetworksCritical 9.3
CVE-2026-116953
F5 BIG-IP iRule GENERICMESSAGE::route can crash TMM and allow remote code execution.
How scary is it?
updated 21 Nov 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list2
Not in the catalog as of our last sync.
Scare-o-meter
Act this week
Serious and within reach of attackers. Schedule the fix this week.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Reachable over the network with no login and no user action; CVSS 9.3.1 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run one of these 2 products in an affected versionF5 BIG-IP / F5 BIG-IP Next for Kubernetes
F5 BIG-IP: >= 21.1.0 and < *, >= 17.5.0 and < *, >= 17.1.0 and < *
F5 BIG-IP Next for Kubernetes: >= 2.4.0 and < *, >= 2.3.0 and < *, >= 2.2.0 and < *
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Recommendation, AI-writtenApply vendor patch/mitigation ASAP; disable or inspect GENERICMESSAGE::route iRules; restrict client access.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. Affects widely deployed F5 BIG-IP appliances; can disrupt traffic and enable remote code execution, impacting enterprise infrastructure.
- CVSS
- 9.3Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.72%chance of exploitation in the next 30 daystop 46% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Not stated by the vendorno fixed release in the CVE record
- Published
- 18 Nov 2026analysed here 19 Nov 2026
Summary
Impact
Remote unauthenticated attacker can crash the TMM (DoS) and potentially achieve remote code execution on the BIG-IP data plane.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| F5 BIG-IP | >= 21.1.0 and < *>= 17.5.0 and < *>= 17.1.0 and < *Vendor says fixed in: not stated | |
| F5 BIG-IP Next for Kubernetes | >= 2.4.0 and < *>= 2.3.0 and < *>= 2.2.0 and < *Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- F5 BIG-IP (TMM/data plane)
- Virtual servers using iRules with GENERICMESSAGE::route
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. This is a stack buffer overflow. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation none, automatable yes, technical impact totalAssessed by CISA 18 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 18 Nov 2026CISA SSVC assessment: exploitation none
- 18 Nov 2026Published1 day later
- 19 Nov 2026CVE record last updated1 day later
- 19 Nov 2026Analysed by vulneraibility.comsame day later
Common questions
Is CVE-2026-116953 being exploited?
Not confirmed. CVE-2026-116953 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.72% probability of exploitation in the next 30 days.
How severe is CVE-2026-116953?
CVE-2026-116953 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-116953?
Not known from our data. No patch reference has been recorded for CVE-2026-116953, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-116953 affect?
CVE-2026-116953 affects F5 BIG-IP (TMM/data plane), Virtual servers using iRules with GENERICMESSAGE::route. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-116953?
Apply vendor patch/mitigation ASAP; disable or inspect GENERICMESSAGE::route iRules; restrict client access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Patches (1)
- my.f5.com /manage/s/article/K000163941
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.