F5 Discloses Six Critical BIG-IP Buffer Overflows That Crash TMM

F5 disclosed six critical BIG-IP stack buffer overflows that let unauthenticated attackers crash TMM and possibly run code; only engineering hotfixes exist.
Table of Contents
    Add a header to begin generating the table of contents

    F5 disclosed six critical stack-based buffer overflow vulnerabilities in the BIG-IP data plane on November 18, each of which lets an unauthenticated attacker crash the Traffic Management Microkernel (TMM) and may allow remote code execution. The fixes are engineering hotfixes only, with no workaround and no scheduled release.

    Six Overflows in the BIG-IP Data Plane

    Each of the six flaws scores 9.8 on CVSS v3.1 and 9.3 on CVSS v4.0. CVE-2026-123637 affects the Access Policy Manager (APM). The other flaws involve iRule commands, including DNS::scrape and PEM::subscriber. F5 says none of them expose the control plane.

    The affected products are BIG-IP, BIG-IP Next for Kubernetes and BIG-IP CNF. TMM handles the traffic that BIG-IP devices process for load balancing and VPN access, so a crash disrupts that traffic at the network edge.

    Configuration Conditions That Limit Which Systems Are Vulnerable

    None of the six flaws applies to every deployment. Each requires a specific configuration on a virtual server: either an iRule that uses a particular vulnerable command, or an APM per-request policy that includes the Client Information and Endpoint Security agents. A BIG-IP system that uses neither is not exposed to the corresponding bug.

    WatchTowr and F5 Share Credit for the BIG-IP Findings

    WatchTowr researcher Sina Kheirkhah reported four of the six. F5 found the other two internally. No exploitation has been reported, and none of the flaws are in CISA’s Known Exploited Vulnerabilities catalog.

    Stack-based buffer overflows in a data plane component are a bug class that can range from a simple process crash to code execution, depending on what an attacker can control in memory. F5’s advisories confirm the crash outcome for all six and describe code execution as a possibility, without saying that a working exploit exists. The vendor’s statement that the control plane is not exposed narrows the blast radius to traffic handling, but a TMM crash on a load balancer or VPN gateway can still interrupt every application behind it.

    F5 Hotfix-Only Remediation for BIG-IP Without a Workaround

    F5 has not scheduled a regular software release for the fixes. Instead, it is offering engineering hotfixes, including BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 and BNK-2.2.5-EHF1 for BIG-IP Next for Kubernetes, with equivalent builds for CNF. F5 warns that hotfixes receive less quality-assurance testing than full releases and carry no warranty.

    No interim workaround exists. Administrators who cannot confirm that their virtual servers avoid the affected iRule commands and APM policy elements must choose between applying an untested hotfix and leaving a crashable data plane in place. The trade-off is unusual for a vendor advisory in this severity class.

    A Seventh Advisory on iControl REST Token Expiry

    F5 published a seventh related advisory covering iControl REST tokens that may not expire as expected. It carries a CVSS v3.1 score of 8.1.

    Relation to the September APM Flaw

    The new bugs are distinct from CVE-2026-94127, an APM flaw F5 disclosed on September 22 that was later exploited and added to the KEV catalog. That history is the reason the new APM-related issue, CVE-2026-123637, draws attention even though nobody has reported attacks against it.

    The pattern matters for defenders because BIG-IP devices sit at the network edge, and an APM bug that was weaponized once has a track record that the new ones do not yet have. Whether attackers move on the new set depends on how much detail researchers and F5 release about the vulnerable commands and the conditions needed to trigger them.

    F5 published 22 advisories on November 18 in total, ten of which covered NGINX. For BIG-IP administrators, the practical question is how many of their virtual servers use the iRule commands and APM policy agents named in the advisories, since that answer determines whether the hotfix risk is worth taking.

    Related Posts