Skip to main content
Mallory
CriticalVulnerability

CVE-2026-120292: Stack-based buffer overflow in F5 BIG-IP MR::message route

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

CVE-2026-120292 is a stack-based buffer overflow in the F5 BIG-IP Traffic Management Microkernel (TMM), affecting BIG-IP and BIG-IP Next for Kubernetes. When a virtual server combines an HTTP profile with an iRule invoking MR::message route, specially crafted requests can terminate TMM and potentially enable remote code execution. The vulnerability affects only the data plane, with no control-plane exposure. The triggering request format has not been 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.

A remote, unauthenticated attacker can terminate TMM, disrupting traffic through the BIG-IP system while the process restarts. Repeated exploitation could prolong the denial of service and interrupt dependent applications even when backend servers remain operational. Remote code execution may also be possible, but its reliability, execution privileges, and additional prerequisites have not been established. There is no direct control-plane exposure.

Mitigation

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

F5 lists no mitigation or workaround. Restricting access to the management interface does not address exposure through an affected traffic-handling virtual server. Installing a fixed build is the only documented remedy.

Remediation

Patch, then assume compromise.

Install the engineering hotfix matching the exact product, release branch, and installed build. For BIG-IP 21.1.0, use BIGIP-21.1.0.4.0.19.3-ENG. For affected 17.5.x base releases, use BIGIP-17.5.1.11.0.61.12-ENG; systems running BIGIP-17.5.1.10.0.7.35-ENG or BIG-IP-17.5.1.10.0.37.35-ENG instead require BIGIP-17.5.1.10.0.80.35-ENG. For affected 17.1.x base releases, use BIGIP-17.1.3.7.0.21.4-ENG; systems running BIGIP-17.1.3.6.0.9.20-ENG instead require BIGIP-17.1.3.6.0.14.20-ENG. Confirm build selection using F5 guidance K000164239. For BIG-IP Next for Kubernetes, install BNK-2.2.5-EHF1, BNK-2.3.4-EHF1, or BNK-2.4.2-EHF1 for the corresponding branch. Contact F5 Support for a replacement hotfix when running a custom engineering build. If the installed branch has no fix, upgrade to a fixed release. Validate application traffic after updating; engineering hotfixes receive less extensive quality assurance than scheduled releases.

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-120292 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-120292 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-120292?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-120292.
Is there a patch for CVE-2026-120292?
Install the engineering hotfix matching the exact product, release branch, and installed build. For BIG-IP 21.1.0, use BIGIP-21.1.0.4.0.19.3-ENG.
How severe is CVE-2026-120292?
CVE-2026-120292 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

27 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 belongs to the group of six flaws described as permitting unauthenticated service disruption through traffic-processing crashes, with possible code execution. Emergency fixes are available, but F5 lists no workaround.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 HTTP profile and an iRule using MR::message route. An unauthenticated remote attacker can terminate or restart 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 flawsA critical stack-based buffer overflow in the group of five flaws affecting BIG-IP APM and iRules. The group permits unauthenticated attackers to terminate TMM or execute arbitrary code remotely on vulnerable configurations; individual component mappings are not provided. Emergency hotfixes are available, with no mitigation measures reported by F5.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 activity6Community discussion across Reddit, Mastodon, and other social sources.