Skip to main content
Mallory
CriticalVulnerability

CVE-2026-116953: Stack-based buffer overflow in F5 BIG-IP GENERICMESSAGE::route

Published Nov 18, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days26 mentions · peak 13 in a dayToday
CVSS9.3Critical · v4
EPSS0.72%55th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-116953CWE-121 · Stack-based Buffer Overflow

CVE-2026-116953 is a stack-based buffer overflow affecting F5 BIG-IP and BIG-IP Next for Kubernetes when a virtual server is configured with an iRule that processes client traffic using GENERICMESSAGE::route. Undisclosed requests can trigger termination of the Traffic Management Microkernel (TMM) and may enable remote code execution. Exploitation is remote and unauthenticated. The vulnerability affects the traffic-processing data plane only, with no control-plane exposure. The precise triggering request structure and faulty implementation logic have not been publicly disclosed.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can terminate TMM, interrupting client traffic and making dependent applications unavailable while the process restarts. Repeated exploitation can sustain service disruption. The stack-based memory corruption may also permit remote code execution on the affected system; code execution is a potential outcome rather than a confirmed capability. The vulnerability does not directly expose the administrative control plane.

Mitigation

If you can’t patch tonight, do this now.

F5 lists no mitigation or workaround. Restricting management-interface access does not address this data-plane vulnerability when an affected virtual server remains reachable.

Remediation

Patch, then assume compromise.

Install the engineering hotfix appropriate to the exact installed branch and build, or upgrade to a release containing the fix. BIG-IP fixed builds are BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, and BIGIP-17.1.3.7.0.21.4-ENG for their respective base-release branches. Systems running BIGIP-17.5.1.10.0.7.35-ENG or BIG-IP-17.5.1.10.0.37.35-ENG require BIGIP-17.5.1.10.0.80.35-ENG; systems running BIGIP-17.1.3.6.0.9.20-ENG require BIGIP-17.1.3.6.0.14.20-ENG. BIG-IP Next for Kubernetes fixes are BNK-2.2.5-EHF1, BNK-2.3.4-EHF1, and BNK-2.4.2-EHF1 for their respective branches. Confirm applicability using F5 advisory K000163941 and hotfix-selection guidance K000164239. Obtain replacement builds from F5 Support for custom engineering hotfix deployments. Validate the installed fixed build and live application traffic after updating.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-116953 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-116953 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-116953?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-116953.
Is there a patch for CVE-2026-116953?
Install the engineering hotfix appropriate to the exact installed branch and build, or upgrade to a release containing the fix. BIG-IP fixed builds are BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, and BIGIP-17.1.3.7.0.21.4-ENG for their respective base-release branches.
How severe is CVE-2026-116953?
CVE-2026-116953 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 0.72% (55th percentile) as of Nov 21, 2026.
Activity feed

Recent activity

26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cryptika blogNews · Nov 21, 20266 Critical F5 BIG-IP Vulnerabilities Could Let Hackers Disrupt Websites and Execute Malicious Code | Cryptika CybersecurityA critical memory-corruption vulnerability affecting BIG-IP iRules configurations. The six critical flaws can allow unauthenticated remote attackers to crash the Traffic Management Microkernel, disrupting websites and other services, and potentially execute code. F5 released emergency hotfixes and reported no exploitation at disclosure.Read more ↗cyber security newsNews · Nov 21, 20266 Critical F5 BIG-IP Vulnerabilities Could Let Hackers Disrupt Websites and Execute Malicious CodeA critical BIG-IP memory-corruption vulnerability affecting iRules configurations. It is one of six data-plane flaws that can disrupt websites and other services through unauthenticated traffic-processing crashes, with possible code execution described for the group.Read more ↗csirt skNews · Nov 20, 2026F5 opravila šesť kritických zraniteľností v BIG-IP | CSIRT.SKCritical stack-based buffer overflow affecting BIG-IP traffic processing when a virtual server has an iRule using GENERICMESSAGE::route. An unauthenticated remote attacker can terminate or restart Traffic Management Microkernel (TMM), causing denial of service, and potentially execute code. The data plane is affected, not the management interface. CVSS v4: 9.3. F5 engineering hotfixes are available.Read more ↗bleeping computerNews · Nov 20, 2026F5 releases emergency patches for critical BIG-IP RCE flawsOne of five critical stack-based buffer overflow flaws collectively affecting BIG-IP APM and iRules. Unauthenticated exploitation can terminate TMM or enable remote arbitrary code execution on vulnerable configurations. The article does not provide a per-CVE component mapping. Emergency hotfixes are available, but F5 reports no mitigation measures.Read more ↗
+11 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.