F5 disclosed six critical stack-based buffer overflow flaws in BIG-IP on November 18, 2026. Each lets an unauthenticated attacker crash the Traffic Management Microkernel (TMM) and may allow remote code execution, but only on virtual servers with a specific setup. F5 has released engineering hotfixes only and lists no workaround.
What happened
F5 rates all six 9.8 on CVSS v3.1 and 9.3 on CVSS v4.0. They sit in the data plane, the part of BIG-IP that handles application traffic, and F5 says the management side is not exposed. Crafted requests, which F5 does not describe, overflow a stack buffer, TMM terminates, and traffic is disrupted until it restarts. None of F5’s advisories reports exploitation. According to The Hacker News, watchTowr researcher Sina Kheirkhah reported four of the flaws and F5 found the other two itself.
Five of the six are in iRules, the scripting feature administrators use to manage traffic; one is in the Access Policy Manager (APM) module. Each needs its own trigger:
| CVE | Setup the virtual server needs |
|---|---|
CVE-2026-123637 | APM per-request policy containing both the Client Information and Endpoint Security agents |
CVE-2026-121805 | iRule using PEM::subscriber on client traffic |
CVE-2026-120292 | HTTP profile plus an iRule using MR::message route |
CVE-2026-120285 | HTTP profile plus an iRule using PSC::ip_address |
CVE-2026-116953 | iRule using GENERICMESSAGE::route on client traffic |
CVE-2026-120722 | iRule using DNS::scrape on client traffic |
Who is affected
For the APM flaw (CVE-2026-123637), F5 lists BIG-IP APM 21.1.0, 17.5.0 through 17.5.1 and 17.1.0 through 17.1.3 as affected, per Cyber Security News’ reading of advisory K000163937. Some of the iRule flaws also affect BIG-IP Next for Kubernetes and BIG-IP CNF. F5 evaluates only versions still in technical support, so an older release missing from its tables has not been shown to be safe.
These are not the APM heap overflow CVE-2026-94127, which F5 disclosed on September 22 and CISA added to its Known Exploited Vulnerabilities catalog the same day. Health-ISAC notes that because the new flaws are in the data plane, locking down administrative ports will not prevent traffic disruption.
What to do
- Inventory virtual servers for the setups in the table above, including every iRule that calls one of those commands (our analysis).
- Match each system’s full installed build to F5’s hotfix guidance (K000164239). For example, APM 17.5.1.11 or an earlier 17.5.1 base build needs
BIGIP-17.5.1.11.0.61.12-ENG, and 21.1.0.4 needsBIGIP-21.1.0.4.0.19.3-ENG. A system already on a custom hotfix needs a new one from F5 support. - Test before wide rollout (our analysis). F5 warns that engineering hotfixes do not get the full QA of scheduled releases and carry no warranty.
- After installing, confirm the running build and that affected virtual servers pass traffic and policies normally. A TMM restart can explain an outage, but it does not by itself show an attacker ran code.
- Do not overlook the same-day lower-rated fixes. The iControl SOAP flaw
CVE-2026-125274(CVSS 8.8) is fixed in BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6.
What we still do not know
F5 has not said what the crafted requests look like, and no exploitation has been reported, which is not the same as none occurring. F5 has not scheduled a regular release containing the fixes. Its advisory for CVE-2026-120722 lists BIG-IP CNF as not vulnerable, while that CVE record, updated November 18, lists CNF as affected, so CNF users should check F5’s latest notes.
Sources: The Hacker News, Nov. 18, 2026; Cyber Security News, Nov. 21, 2026; Health-ISAC bulletin via AHA, Nov. 19, 2026.
Leave a Reply