F5 Urgent Patches Released for Six Critical BIG-IP Vulnerabilities Carrying 9.8 CVSS Scores

F5 has issued urgent advisories and emergency patches to address six critical vulnerabilities affecting its widely deployed BIG-IP enterprise networking infrastructure. The newly disclosed security flaws can be exploited by unauthenticated remote attackers to trigger a crash in the Traffic Management Microkernel, disrupting critical network operations until the underlying service restarts. Furthermore, the technology vendor has cautioned that these severe software bugs carry the potential to facilitate arbitrary remote code execution under specific conditions.

The vulnerabilities, which have been assigned a maximum CVSS v3.1 severity rating of 9.8 and a 9.3 rating under CVSS v4.0, directly impact the data plane of BIG-IP systems. The data plane is responsible for processing the vast majority of network traffic flowing through the enterprise infrastructure, making the potential impact of these flaws exceptionally high for organizations relying on the platform for application delivery and security.

According to technical disclosures published by the company, each of the six critical vulnerabilities requires a specific configuration on a targeted virtual server to be successfully exploited. Five of the flaws reside within iRules, a powerful and flexible scripting feature used extensively by network administrators to manipulate, inspect, and direct traffic passing through BIG-IP devices. The remaining critical vulnerability is located within the BIG-IP Access Policy Manager (APM) module, requiring a specific combination of policy agents to be active.

Security researchers played a prominent role in identifying the issues. Sina Kheirkhah, a security researcher affiliated with WatchTowr, independently discovered four of the critical vulnerabilities, while internal security audits and testing by F5 uncovered the remaining two. At the time of the advisories, neither F5 nor external researchers have observed any active exploitation of these specific zero-day or newly patched vulnerabilities in the wild.

In addition to traditional BIG-IP hardware and software deployments, the security advisories note that some of these critical flaws also impact modern cloud-native architectures. Affected products include BIG-IP Next for Kubernetes and BIG-IP Cloud-Native Edition (CNF), widening the potential attack surface for organizations transitioning their application delivery layers to containerized environments.

F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE

The discovery of these vulnerabilities underscores the continuous security challenges associated with complex enterprise networking and application delivery controllers. Because the management side of BIG-IP remains unexposed in these scenarios, the risk profile is heavily concentrated on the data plane where high-volume user and application traffic is actively processed.

Addressing the Six Critical Flaws

The response from F5 involves a comprehensive set of advisories detailing 22 distinct security issues across its product ecosystem, including 10 vulnerabilities specifically affecting NGINX products. However, the six critical BIG-IP flaws stand out due to their severity scores and the absence of traditional workarounds.

For organizations running affected versions of BIG-IP, F5 has stated that there are currently no configuration workarounds available to mitigate the risk while awaiting a standard software update. Instead, the company has released emergency engineering hotfixes designed to patch the underlying stack-based buffer overflows.

Engineering hotfixes represent specialized builds issued by software vendors outside of their regular, scheduled maintenance and release cycles. Because of their expedited nature, F5 has issued specific guidance regarding their deployment. The company notes that engineering hotfixes do not undergo the same extensive quality assurance and rigorous assessment processes applied to its standard scheduled software releases. Consequently, standard corporate hotfix policies emphasize that these emergency builds are provided without the typical warranties or formal performance guarantees associated with general-availability software.

Furthermore, environments operating on a custom engineering hotfix often require tailored maintenance pathways, meaning administrators must coordinate closely with F5 support teams to ensure future stability and upgrade paths. For cloud-native deployments, specific hotfix builds have been made available to address the risks. For instance, BIG-IP Next for Kubernetes requires updates to specific engineering hotfix versions depending on the active branch, while BIG-IP CNF installations face similar requirements for specific CVE identifiers.

F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE

F5 has emphasized that its security assessments and patch provisioning apply strictly to software versions that remain within active technical support lifecycles. Organizations utilizing older, end-of-life releases that do not appear in the vendor’s updated advisory tables have not been verified as safe and face heightened security risks unless they upgrade to supported versions.

Broader Context and Prior Incidents

The disclosure of these six stack-based buffer overflows comes just months after F5 addressed another high-profile security issue within its ecosystem. In late September, the company disclosed CVE-2026-94127, a critical heap-based buffer overflow vulnerability located in the BIG-IP APM module when configured to act as an OAuth authorization server. That zero-day vulnerability, which also allowed unauthenticated remote code execution, was rapidly weaponized by malicious actors in the wild. Shortly after its disclosure, the U.S. Cybersecurity and Infrastructure Security Agency added the APM flaw to its Known Exploited Vulnerabilities catalog, prompting emergency patching across federal agencies and private enterprises alike.

While the newly disclosed batch of six vulnerabilities shares similarities in terms of potential impact—such as service disruption and potential remote code execution—they differ fundamentally in their underlying technical mechanics and prerequisite configurations. Unlike the heap-based overflow seen in September, the latest six flaws are stack-based buffer overflows residing primarily within the iRules traffic management engine and specific APM agent configurations.

In addition to the top-tier critical vulnerabilities, the latest batch of advisories covers a series of lower-rated security flaws affecting both BIG-IP and BIG-IQ management platforms. Each of these secondary vulnerabilities carries its own distinct CVSS v3.1 rating and corresponding mitigation path, ensuring that enterprise security teams have the necessary patch information to secure their entire networking stack.

As organizations review the latest advisories, cybersecurity professionals recommend prioritizing the assessment of virtual server configurations to determine exposure to the iRules and APM prerequisites. Given the lack of administrative workarounds, administrators managing exposed systems face an urgent need to evaluate and deploy the provided engineering hotfixes to maintain the integrity and availability of their enterprise traffic management infrastructure.