Skip to main content
Mallory
CriticalVulnerability

CVE-2026-121805: Stack-Based Buffer Overflow in F5 BIG-IP PEM::subscriber iRules Processing

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

CVE-2026-121805 is a stack-based buffer overflow affecting F5 BIG-IP Policy Enforcement Manager (PEM) and BIG-IP Next for Kubernetes when a virtual server has an iRule that processes client traffic using the PEM::subscriber command. A remote, unauthenticated attacker can send specially crafted requests that terminate the Traffic Management Microkernel (TMM), causing denial of service and potentially remote code execution. The vulnerability affects only the data plane, with no control plane exposure. Affected releases include BIG-IP PEM 17.1.0–17.1.3, 17.5.0–17.5.1, and 21.1.0, and BIG-IP Next for Kubernetes 2.2.0–2.2.5, 2.3.0–2.3.4, and 2.4.0–2.4.2. The precise triggering requests and underlying vulnerable code path have 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.

Successful exploitation terminates TMM and disrupts traffic while the process restarts, potentially making applications and other services traversing the affected system unavailable even when backend servers remain operational. Remote code execution may also be possible, but the conditions necessary to achieve it have not been disclosed. The vulnerability does not directly expose the administrative control plane.

Mitigation

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

F5 lists no interim 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 F5 engineering hotfix appropriate to the exact product, release branch, and installed build. For BIG-IP PEM, listed fixes are BIGIP-21.1.0.4.0.19.3-ENG for 21.1.0; BIGIP-17.5.1.11.0.61.12-ENG for affected 17.5.x base releases; and BIGIP-17.1.3.7.0.21.4-ENG for affected 17.1.x base releases. Systems running BIGIP-17.1.3.6.0.9.20-ENG require BIGIP-17.1.3.6.0.14.20-ENG. 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. Confirm build selection against F5 advisories K000163946 and K000164239; obtain a replacement build from F5 Support for custom engineering builds. 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. Upgrade to a fixed branch if no fix exists for the installed branch. BIG-IP CNF applicability is inconsistently identified and requires confirmation with F5. Engineering hotfixes receive less extensive quality assurance than scheduled releases; test where feasible and validate live traffic after deployment.

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-121805 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-121805 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-121805?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-121805.
Is there a patch for CVE-2026-121805?
Install the F5 engineering hotfix appropriate to the exact product, release branch, and installed build. For BIG-IP PEM, listed fixes are BIGIP-21.1.0.4.0.19.3-ENG for 21.1.0; BIGIP-17.5.1.11.0.61.12-ENG for affected 17.5.x base releases; and BIGIP-17.1.3.7.0.21.4-ENG for affected 17.1.x base releases.
How severe is CVE-2026-121805?
CVE-2026-121805 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

31 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 among six flaws that can let unauthenticated remote attackers disrupt live traffic, with potential code execution also reported for the group. Patches exist, but no workaround is listed.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 PEM::subscriber. 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 flawsOne of five critical stack-based buffer overflow vulnerabilities collectively described as affecting BIG-IP APM and iRules. Unauthenticated attackers can terminate the Traffic Management Microkernel (TMM) or execute arbitrary code remotely on vulnerable configurations. The article does not map individual flaws to specific components. Emergency hotfixes are available; F5 reports no mitigation measures. Exploitation has not been flagged by F5, but the article does not establish that none has occurred.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 activity10Community discussion across Reddit, Mastodon, and other social sources.