As reported by The Hacker News, F5 disclosed six critical vulnerabilities in BIG-IP that can crash the Traffic Management Microkernel (TMM) without authentication and may allow remote code execution. All six are stack-based buffer overflows in the data plane, rated 9.8 (CVSS v3.1) and 9.3 (CVSS v4.0). The only available fixes are engineering hotfixes — interim builds that F5 warns do not undergo full QA and carry no warranty.
Vulnerability Details
| CVE | Trigger Condition | Affected Products |
|---|---|---|
| CVE-2026-123637 | APM per-request policy with both Client Information and Endpoint Security agents | BIG-IP APM |
| CVE-2026-121805 | iRule using PEM::subscriber on client traffic | BIG-IP PEM, BIG-IP Next for Kubernetes, BIG-IP CNF |
| CVE-2026-120292 | HTTP profile + iRule using MR::message route | BIG-IP (all modules), BIG-IP Next for Kubernetes |
| CVE-2026-120285 | HTTP profile + iRule using PSC::ip_address | BIG-IP (all modules), BIG-IP Next for Kubernetes, BIG-IP CNF |
| CVE-2026-116953 | iRule using GENERICMESSAGE::route on client traffic | BIG-IP (all modules), BIG-IP Next for Kubernetes |
| CVE-2026-120722 | iRule using DNS::scrape on client traffic | BIG-IP DNS, BIG-IP Next for Kubernetes |
Severity: Critical (CVSS 9.8 v3.1 / 9.3 v4.0) | Patch Status: Engineering hotfixes available, no scheduled release fix listed, no workaround | Active Exploitation: None reported | Attack Surface: Data plane only; management plane not exposed
Why This Matters
The critical detail here is specificity. Unlike many BIG-IP advisories that affect broadly deployed configurations, each of these six flaws requires a particular iRule command or APM agent combination to be active on a virtual server. This means many organizations may be unaffected — but those who are affected are likely high-value targets: telecom and service provider environments using PEM for subscriber management, enterprises with complex traffic routing via MR or GENERICMESSAGE, and organizations leveraging APM for endpoint posture checks.
The TMM is the core data-plane process handling virtually all network traffic. A crash causes a full traffic disruption until TMM restarts. For load balancers sitting in front of production applications, this translates to complete service outages — and if RCE is achieved, the attacker controls the appliance that guards your perimeter.
F5's own acknowledgment that engineering hotfixes "do not undergo the extensive QA assessment of scheduled software releases" creates a genuine dilemma for change-averse environments. But given the CVSS scores and potential RCE, delaying is the riskier path.
Who Is at Risk
Even if your BIG-IP deployment is internet-facing, these flaws are only exploitable if the specific iRule or APM configuration is present. Inventory your virtual server configurations first — that determines your actual exposure.
Shield53 Recommendations
Immediate Actions
- Audit iRules and APM policies across all virtual servers. Search for the six trigger commands:
PEM::subscriber,MR::message route,PSC::ip_address,GENERICMESSAGE::route,DNS::scrape, and APM per-request policies combining Client Information with Endpoint Security agents. - Request and apply the engineering hotfix from F5 support for any affected virtual server. F5 requires a support contract to obtain hotfixes — confirm your entitlement is active.
- Isolate affected virtual servers where hotfix deployment must wait for maintenance windows. Consider temporarily disabling the triggering iRule or APM agent combination if the business impact is tolerable.
- Deploy WAF or IDS signatures to detect anomalous traffic targeting the affected virtual servers. While no public PoC exists, monitor for unusual packet patterns or repeated connection attempts to affected VIPs.
- Plan hotfix rollback — given F5's QA caveat, snapshot or backup the configuration before applying, and validate traffic processing behavior immediately after deployment.
- Watch for the scheduled release fix and migrate off the engineering hotfix once a fully tested version becomes available.
Detection Guidance
Monitor TMM crash logs (/var/log/ltm) for unexpected restarts, which may indicate exploitation attempts. Enable iRule event logging on affected virtual servers to capture anomalous traffic patterns preceding any TMM crash. Correlate with SNMP traps for TMM process failures in your SIEM.