I'm a few days late on this one. F5 published its BIG-IP advisories on November 18, and the headline is six separate stack buffer overflows, each rated CVSS 9.8, all in TMM, the engine that actually moves your traffic. No login needed. No exploitation reported yet. That last part is the window you want to use.
What F5 Fixed
Per F5's advisories as summarized by the Canadian Centre for Cyber Security, Censys and SecurityOnline:
- CVE-2026-123637, BIG-IP APM. Triggered when APM is provisioned and a virtual server uses a per-request policy that includes both the Client Information and Endpoint Security agents.
- Five iRule bugs: CVE-2026-116953 (
GENERICMESSAGE::route), CVE-2026-120285 (PSC::ip_address), CVE-2026-120292 (MR::message route), CVE-2026-120722 (DNS::scrape) and CVE-2026-121805 (PEM::subscriber). Each only matters if an iRule on your box uses that command, and some need a specific profile. - Impact: a crafted request can make TMM terminate (traffic stops) and F5 says it "may" lead to remote code execution.
- Affected: BIG-IP 21.1.0, 17.5.0 to 17.5.1 and 17.1.0 to 17.1.3, plus BIG-IP Next for Kubernetes 2.2 to 2.4 for several of the iRule bugs. The Canadian advisory also lists BIG-IP CNF and BIG-IQ builds, so check F5's own articles for your exact product.
- Fixes: engineering hotfixes (the
-ENGbuilds) for 21.1.0, 17.5.1 and 17.1.3, not a regular point release. F5 lists no workaround. - Bonus bug: CVE-2026-120718 (CVSS 8.1), where iControl REST tokens may not expire as expected. That one is fixed in standard releases.
Censys says it sees over two million internet-facing F5 BIG-IP web properties. That's not a count of vulnerable systems (the bugs depend on configuration), but it tells you how big the haystack is.
Credit where it's due: F5 shipped six critical fixes at once with clear trigger conditions, and watchTowr's Sina Kheirkhah is credited with several of the reports. Clear "you're only affected if" conditions are a gift to defenders. Use them.
The Bigger Picture
Standard disclosure: I work at Zscaler, which does not sell load balancers, so take my architecture opinions with that in mind. Every vendor ships bugs, mine included. But this is another reminder that the box at the front door parses everything the internet sends it. iRules are wonderful precisely because they let you run custom logic on untrusted traffic. That's also why an overflow in an iRule command is a 9.8.
The other note: BIG-IP APM had an RCE added to CISA's KEV catalog in September (CVE-2026-94127). Attackers know these boxes, and the gap between "no exploitation known" and "exploited" for edge devices has been shrinking all year.
What To Do
- Search your iRules for
GENERICMESSAGE::route,PSC::ip_address,MR::message,DNS::scrapeandPEM::subscriber. If none show up, the iRule bugs don't apply to you. - Check APM per-request policies for the Client Information plus Endpoint Security agent combination.
- If you match, schedule the hotfix now. Engineering hotfixes need the usual testing, so start the change process today rather than waiting for a point release.
- Restrict the management interface anyway. It doesn't fix these data-plane bugs, but it's cheap and it closes off the next one.
- Watch for TMM restarts. Unexpected TMM cores on an affected config are worth investigating, not just rebooting.
- Rotate iControl REST tokens and delete ones you don't need, given CVE-2026-120718.
Bottom Line
Six 9.8s, no known exploitation, and clear conditions for who's affected. That's the best version of a bad week. Do the iRule search this weekend and patch what matches before somebody writes the exploit.
Sources: Canadian Centre for Cyber Security AV26-1178, Censys advisory, SecurityOnline, GBHackers, F5 K000163937