TL;DR
F5 published seven F5 BIG-IP security advisories on November 18, 2026. Six of them describe stack-based buffer overflows rated CVSS 9.8 that may allow remote code execution without a login. The seventh lets stolen iControl REST tokens live longer than they should.
CVE-2026-123637 hits BIG-IP APM, while five more bugs sit in iRule commands on BIG-IP and BIG-IP Next for Kubernetes. Each one can crash the Traffic Management Microkernel (TMM) and may lead to code execution. F5 reports no exploitation, and none of the seven appear in CISA’s KEV catalog.
- Total: 7 CVEs
- Severity: 7 Critical
- Actively exploited: None confirmed
- Highest severity: 9.8 (Critical · CVSSv3) — CVE-2026-123637
- Action: Apply the latest security updates now
Notable CVEs
| CVE | CVSS (CVSSv3) | Type | Fixed in | Status |
|---|---|---|---|---|
| CVE-2026-123637 | 9.8 | APM | BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.5.1.10.0.80.35-ENG (+2) | Not exploited |
| CVE-2026-116953 | 9.8 | iRule | BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.5.1.10.0.80.35-ENG (+5) | Not exploited |
| CVE-2026-120285 | 9.8 | iRule | BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.5.1.10.0.80.35-ENG (+8) | Not exploited |
| CVE-2026-120292 | 9.8 | iRule | BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.5.1.10.0.80.35-ENG (+5) | Not exploited |
| CVE-2026-120722 | 9.8 | iRule | BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.5.1.10.0.80.35-ENG (+8) | Not exploited |
| CVE-2026-121805 | 9.8 | iRule | BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.5.1.10.0.80.35-ENG (+8) | Not exploited |
| CVE-2026-120718 | 8.1 | iControl REST | 21.1.0.2, 17.5.1.10, 17.1.3.6 (+1) | Not exploited |
Why It Matters
Attackers Target F5 BIG-IP
BIG-IP appliances sit at the network edge and handle traffic, VPN access and load balancing. That position makes them a common target. CISA’s Known Exploited Vulnerabilities catalog added a BIG-IP APM flaw, CVE-2026-94127, in September 2026. In March, it also listed a BIG-IP bug from 2025.
No Login Required
Each of the six overflow advisories uses nearly the same wording. They say the flaw “allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may allow the attacker to perform RCE.” Furthermore, F5 notes that “traffic is disrupted while the TMM process restarts.”
On the other hand, F5 stresses that “there is no control plane exposure; this is a data plane issue only.”
How the Attack Works
F5 does not describe the exact requests. However, every overflow depends on a specific configuration on a virtual server.
BIG-IP APM (CVE-2026-123637)
This flaw needs APM to be provisioned. A per-request policy must also include the Client Information and Endpoint Security agents. Under those conditions, the BIG-IP APM advisory says “undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate.”
Four BIG-IP iRule Command Flaws
iRules are scripts that admins write to inspect and steer traffic. Next, four bugs depend on iRules that use specific commands:
- CVE-2026-116953: the GENERICMESSAGE::route command, per the GENERICMESSAGE advisory
- CVE-2026-120285: the PSC::ip_address command with an HTTP profile, per the PSC::ip_address advisory
- CVE-2026-120292: the MR::message route command with an HTTP profile, per the MR::message advisory
- CVE-2026-120722: the DNS::scrape command on BIG-IP DNS, per the DNS::scrape advisory
BIG-IP PEM (CVE-2026-121805)
Similarly, this bug needs an iRule that uses the PEM::subscriber command. The PEM::subscriber advisory lists BIG-IP PEM and BIG-IP Next for Kubernetes as affected. F5 found this flaw and the DNS::scrape bug internally.
iControl REST Tokens (CVE-2026-120718)
This one is different. According to the iControl REST advisory, tokens “may not expire as expected in all scenarios.” As a result, an attacker who already holds a token “may be able to extend its expiry lifetime unless the token owner deletes it.” F5 rates it 8.1 under CVSS 3.1.
Affected Versions
F5 BIG-IP
- 21.1.0
- 17.5.0 to 17.5.1
- 17.1.0 to 17.1.3
BIG-IP Next for Kubernetes
- 2.4.0 to 2.4.2, 2.3.0 to 2.3.4 and 2.2.0 to 2.2.5 (five iRule flaws)
BIG-IQ, F5 Insight and BIG-IP CNF are not affected. The APM, DNS and PEM bugs only hit those modules.
Patch and Mitigation
For the six overflow bugs, F5 lists engineering hotfixes rather than standard releases. These include BIGIP-21.1.0.4.0.19.3-ENG3, BIGIP-17.5.1.11.0.61.12-ENG3 and BIGIP-17.1.3.7.0.21.4-ENG3. Kubernetes customers need BNK-2.4.2-EHF13, BNK-2.3.4-EHF13 or BNK-2.2.5-EHF13. F5 lists no mitigation for these six.
The token flaw is fixed in standard F5 BIG-IP releases 21.1.0.2, 17.5.1.10 and 17.1.3.6. Until you upgrade, F5 advises: “Modify scripts that create REST tokens to delete them at the end of their useful life.”
Next Steps
- Search every BIG-IP iRule for the five affected commands, including PEM::subscriber.
- Remove or rewrite iRules that use those commands if you cannot patch yet.
- Check APM per-request policies for the Client Information and Endpoint Security agents.
- Apply hotfixes to internet-facing virtual servers first.
Finally, F5 credits Sina Kheirkhah of watchTowr with four of these F5 BIG-IP reports. Patch soon, because BIG-IP bugs have drawn attacks this year.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!