Introduction
F5 has disclosed a critical data plane flaw in BIG-IP. When a virtual server iRule uses the PEM::subscriber command, a remote, unauthenticated attacker has a path to crash the Traffic Management Microkernel (TMM) and possibly execute code. Traffic is disrupted every time TMM restarts, and F5 states that no mitigation exists short of installing its engineering hotfixes.
CVE-2026-121805 carries a CVSS v3.1 score of 9.8 and a CVSS v4.0 score of 9.3, and F5 classifies it as CWE-121, a stack-based buffer overflow. It was published on November 18, 2026, and affects both BIG-IP and BIG-IP Next for Kubernetes releases.
Technical information
Root cause
F5 attributes the issue to a stack-based buffer overflow (CWE-121) reachable when client traffic is processed by an iRule that calls PEM::subscriber. The advisory describes the trigger only as "undisclosed requests" and does not publish the request format, the vulnerable code path, or a proof of concept. So we are not going to speculate about where in the PEM::subscriber handling the overflow occurs. The public record establishes the precondition, the weakness class, and the impact, but not the low-level mechanics.
Attack flow
Based on what F5 has disclosed, the attack sequence looks like this:
- The target has a virtual server with an iRule that processes client traffic using the PEM::subscriber command. This configuration is the publicly stated precondition.
- A remote attacker with no credentials sends specific, undisclosed requests to that virtual server. The attack surface is the data plane, and F5 states there is no control plane exposure.
- Processing those requests causes TMM to terminate. F5 classifies the underlying weakness as a stack-based buffer overflow.
- Traffic through the BIG-IP system is disrupted while the TMM process restarts, producing a denial of service.
- F5 states the issue may lead to remote code execution. The advisory does not describe the conditions required to achieve RCE, and it does not report a confirmed successful exploit.
Scope notes
- F5 is explicit that this is a data plane issue with no control plane exposure.
- The disclosed trigger requires an iRule using PEM::subscriber on a virtual server. Inventorying iRules for this command is the practical first step in determining exposure.
- F5 states there is no mitigation and identifies no workaround. The action it specifies is installing the applicable engineering hotfix.
Exploitation status
F5's advisory does not state that this vulnerability has been exploited. The CISA Known Exploited Vulnerabilities catalog, as inspected for this summary, did not list CVE-2026-121805, and we found no CVE-specific threat actor attribution or confirmation of exploitation in the wild. That supports treating exploitation status as unconfirmed, which is not the same as ruled out.
Affected systems and versions
F5's advisory lists the following vulnerable releases and corresponding fixes:
- BIG-IP 21.x: version 21.1.0 is vulnerable. Fix: BIGIP-21.1.0.4.0.19.3-ENG
- BIG-IP 17.x: versions 17.5.0 through 17.5.1 and 17.1.0 through 17.1.3 are vulnerable. Fixes: BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.5.1.10.0.80.35-ENG, BIGIP-17.1.3.7.0.21.4-ENG, BIGIP-17.1.3.6.0.14.20-ENG
- BIG-IP Next for Kubernetes 2.x: versions 2.4.0 through 2.4.2 are vulnerable. Fix: BNK-2.4.2-EHF1
- BIG-IP Next for Kubernetes 2.x: versions 2.3.0 through 2.3.4 are vulnerable. Fix: BNK-2.3.4-EHF1
- BIG-IP Next for Kubernetes 2.x: versions 2.2.0 through 2.2.5 are vulnerable. Fix: BNK-2.2.5-EHF1
Vulnerable configuration: a virtual server with an iRule that processes client traffic using the PEM::subscriber command.
Three qualifications apply to this list:
- All listed fixes are engineering hotfixes. F5 notes that engineering hotfixes do not undergo the extensive QA assessment applied to scheduled software releases, so factor that into change planning and confirm the exact branch and build against the advisory before applying.
- F5's advisory table lists BIG-IP CNF as not vulnerable, while The Hacker News reports that the CVE record lists CNF as affected and names CNF hotfixes. The sources do not resolve this conflict, so CNF operators should seek clarification from F5 rather than treating either classification as settled.
- F5 does not evaluate versions that have reached End of Technical Support. An unsupported version missing from the list should not be read as confirmed unaffected.
Vendor security history
F5 describes itself in its 2025 annual report as a global leader in application delivery and security solutions, serving application and API deployments across on-premises, cloud, and network-edge environments. That is the company's own positioning, not an independent market ranking. BIG-IP is its application delivery and security services platform, which provides security and traffic management functions.
In 2025, F5 disclosed a separate security incident in which, according to F5, a sophisticated nation-state threat actor maintained long-term access to certain F5 systems, including BIG-IP product development and engineering knowledge platforms. F5 said the actor exfiltrated files containing some BIG-IP source code and information about undisclosed BIG-IP vulnerabilities, and that its containment actions were successful with no new unauthorized activity observed. The sources reviewed do not connect that incident or actor to CVE-2026-121805.
References
- NVD entry for CVE-2026-121805
- CVE.org record for CVE-2026-121805
- F5 advisory K000163946: BIG-IP iRule vulnerability CVE-2026-121805
- The Hacker News: F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE
- CISA Known Exploited Vulnerabilities Catalog
- F5 Security Incident (K000154696)
- F5 BIG-IP Application Delivery and Security Services
- F5 2025 Annual Report (SEC filing)



