CVE-2026-121805: Stack-Based Buffer Overflow in F5 BIG-IP PEM::subscriber iRules Processing
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
Recent activity
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.