F5 Discloses Six Critical BIG-IP Vulnerabilities That Crash TMM and May Enable Remote Code Execution

F5 has disclosed six critical vulnerabilities in BIG-IP products that allow unauthenticated attackers to crash the Traffic Management Microkernel and potentially achieve remote code execution. Each flaw requires a specific configuration on a virtual server, such as particular iRule commands or APM policy agents. The issues affect multiple modules including BIG-IP PEM, DNS, APM, and cloud-native variants like BIG-IP Next for Kubernetes and BIG-IP CNF. All six vulnerabilities received CVSS v3.1 scores of 9.8 and CVSS v4.0 scores of 9.3. F5 has released only engineering hotfixes with no workarounds or scheduled releases listed as fixes. The flaws were reported by WatchTowr researcher Sina Kheirkhah and discovered internally by F5. They differ from a previously exploited APM heap-based buffer overflow disclosed in September.

The Hacker NewsTranslated from English

Read at source

F5 has warned of six critical vulnerabilities in its BIG-IP platform that can crash the Traffic Management Microkernel (TMM) without authentication, disrupting network traffic until the kernel restarts. The flaws may also permit remote code execution in certain setups. All six issues carry CVSS v3.1 scores of 9.8 and CVSS v4.0 scores of 9.3.

The vulnerabilities reside in the data plane and require specific configurations on virtual servers. Five affect iRules while one impacts the APM module. Affected products include standard BIG-IP deployments, BIG-IP Next for Kubernetes, and BIG-IP CNF.

Details of the Six Critical Flaws

  • CVE-2026-123637: Requires an APM per-request policy containing both the Client Information agent and Endpoint Security agents. Affects BIG-IP APM only.
  • CVE-2026-121805: Requires an iRule using PEM::subscriber on client traffic. Affects BIG-IP PEM, BIG-IP Next for Kubernetes, and BIG-IP CNF.
  • CVE-2026-120292: Requires an HTTP profile and an iRule using MR::message route. Affects all BIG-IP modules and BIG-IP Next for Kubernetes.
  • CVE-2026-120285: Requires an HTTP profile and an iRule using PSC::ip_address. Affects all BIG-IP modules, BIG-IP Next for Kubernetes, and BIG-IP CNF.
  • CVE-2026-116953: Requires an iRule using GENERICMESSAGE::route on client traffic. Affects all BIG-IP modules and BIG-IP Next for Kubernetes.
  • CVE-2026-120722: Requires an iRule using DNS::scrape on client traffic. Affects BIG-IP DNS and BIG-IP Next for Kubernetes.

F5 released engineering hotfixes for the affected versions but warned that these builds do not undergo the same QA as scheduled releases and come without warranty. No workarounds are available. The company also published six additional medium-severity flaws affecting BIG-IP and BIG-IQ that have their own fixes.

Four of the critical issues were reported by WatchTowr researcher Sina Kheirkhah; the remaining two were found by F5. None of the flaws have been observed in active exploitation according to current advisories.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulns & Exploits

Microsoft Entra Connect Health Flaw Exploited to Access Tenant Metadata and Admin Emails
GnuPG Warns of Critical Double-Free Flaw in GPGME Exposing App Data to Malicious OpenPGP Keys
CISA Adds Four Critical Flaws in Apache Roller, Cisco Expressway, SAP NetWeaver, and VMware vCenter to Known Exploited Vulnerabilities Catalog