What changed
Five critical paths share a traffic-process failure
F5's 18 November out-of-band notification includes five BIG-IP flaws: CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953 and CVE-2026-123637. The individual advisories describe conditions involving BIG-IP APM policies or particular iRule commands. Unauthenticated requests can terminate the Traffic Management Microkernel, disrupting traffic, and may permit remote code execution in vulnerable configurations.
These are data-plane issues, according to F5. The advisories do not establish that every BIG-IP deployment is exposed, nor do they report exploitation in the wild. F5 has issued engineering hotfixes and warns that selecting the right build requires attention to the running branch.
Check the configuration, not just the product name
Defender workflow
Make the emergency patch review specific
- 1
Map active features. Inventory BIG-IP versions, provisioned APM modules, relevant per-request policies and iRules using the affected commands. Include virtual servers reachable from untrusted networks.
- 2
Select the correct fix. Use each F5 advisory's affected-version table and the engineering hotfix instructions. Record the exact build installed; a general product update may not contain the required engineering hotfix.
- 3
Watch the traffic process. Review TMM restarts and unusual request bursts around affected virtual servers. A restart is a lead to investigate, not proof that one of these flaws was exploited.
Defender note
A stable control plane can hide a troubled data plane
Administrators may still be able to log into the management interface while TMM is repeatedly failing. Correlate traffic interruption with TMM logs and the specific virtual-server configuration. That gives the team a much stronger signal than a broad alert for any BIG-IP restart.