JupiteX Get the app
Defence & Security19 Nov 2026 · about 6 min

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

The brief

The most serious possibility is remote code execution: F5 says the six vulnerabilities may allow an attacker to run code without logging in. They can also crash the Traffic Management Microkernel, or TMM, which processes almost all BIG-IP network traffic. A crash can disrupt traffic until TMM restarts. The vulnerabilities are stack-based buffer overflows in BIG-IP’s data plane. They are not triggered by every installation: each requires a particular configuration on a virtual server. For example, one needs an iRule using DNS::scrape on client traffic; another needs an APM per-request policy with two specified agents. F5 rates all six 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0. Its advisories do not say the flaws have been exploited. F5 has released engineering hotfixes, but lists no workaround before installation. The company cautions that hotfixes receive less extensive quality assessment than scheduled releases, and a custom hotfix requires another one from support.

01

What can an attacker do through these six vulnerabilities, even without logging in?

The most serious possibility is remote code execution: F5 says the six vulnerabilities may allow an attacker to run code without logging in. They can also crash the Traffic Management Microkernel, or TMM, which processes almost all BIG-IP network traffic. A crash can disrupt traffic until TMM restarts.

The vulnerabilities are stack-based buffer overflows in BIG-IP’s data plane. They are not triggered by every installation: each requires a particular configuration on a virtual server. For example, one needs an iRule using DNS::scrape on client traffic; another needs an APM per-request policy with two specified agents.

F5 rates all six 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0. Its advisories do not say the flaws have been exploited. F5 has released engineering hotfixes, but lists no workaround before installation. The company cautions that hotfixes receive less extensive quality assessment than scheduled releases, and a custom hotfix requires another one from support.

02

How many critical flaws are involved, how severe are they rated, and which BIG-IP products or modules can be affected?

There are six critical vulnerabilities, and F5 rates every one 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0. All are stack-based buffer overflows in the data plane. Each can crash TMM, disrupting traffic until it restarts; F5 also warns that remote code execution may be possible.

Five flaws require an iRule with a specific command or use, while one requires an APM per-request policy with both Client Information and Endpoint Security agents. The affected products vary: some flaws affect BIG-IP across all modules, while others are limited to APM, PEM, or DNS. Several also affect BIG-IP Next for Kubernetes.

BIG-IP CNF is listed as affected for CVE-2026-121805 and CVE-2026-120285. For CVE-2026-120722, F5’s advisory says CNF is not vulnerable, but the updated CVE record lists it as affected. F5 published engineering hotfixes; the article does not list a workaround before installation.

03

Why does exploiting each flaw require a particular iRule or APM policy on a virtual server?

A virtual server is the setting named in the advisories: each critical flaw requires a particular iRule or APM policy there. That matters because the vulnerabilities are tied to specific BIG-IP features and commands, rather than being described as affecting every configuration automatically.

For example, CVE-2026-120722 requires an iRule using DNS::scrape on client traffic. CVE-2026-120292 requires an HTTP profile plus an iRule using MR::message route. The APM flaw, CVE-2026-123637, requires a per-request policy containing both the Client Information agent and Endpoint Security agents.

The source does not explain the internal reason each setting is necessary. In practical terms, the listed prerequisites identify configurations that invoke the affected feature or code path. Administrators can compare their virtual-server settings with the advisory requirements when assessing exposure. F5 lists engineering hotfixes as the fixes and says there is no workaround until a hotfix is installed.

04

What is the Traffic Management Microkernel, or TMM, and why can a crash disrupt traffic?

TMM stands for Traffic Management Microkernel. The source describes it as the BIG-IP component that processes almost all of the system’s network traffic. That makes it central to BIG-IP’s traffic-handling work, rather than a user-facing management interface.

In general networking terms, a microkernel is a core software component that performs essential system functions. Here, the article’s concrete point is simpler: TMM processes traffic, and the six vulnerabilities can crash it. The source does not detail TMM’s internal architecture or how it handles individual connections.

The impact follows from that role. F5 says a TMM crash disrupts traffic until TMM restarts. The vulnerabilities affect the data plane, while F5 says the management side is not exposed. The company also warns that remote code execution may be possible, but its advisories do not say the six flaws have been exploited. Engineering hotfixes are the listed fixes.

05

What is the difference between a network device’s data plane and management plane, and why does that distinction matter here?

In general networking terms, the data plane is the part of a device that handles traffic moving through it. The management plane is used to configure, monitor, and administer the device. This is a foundational distinction; the article itself says BIG-IP’s data plane processes almost all its network traffic and that the management side is not exposed.

The six flaws are stack-based buffer overflows in the data plane. They require specified settings on a virtual server, such as an iRule or an APM policy. A successful crash can stop TMM, which processes traffic, and disrupt service until it restarts.

The distinction helps explain the kind of system function at risk: these flaws concern traffic processing, not an exposed management interface, according to F5. It does not mean every configuration is affected, because each vulnerability has its own prerequisites. F5 says the flaws may also allow remote code execution, and has issued engineering hotfixes; the advisories give no workaround before installation.

06

What is a stack-based buffer overflow, and how can it cause a crash or let an attacker run code?

A stack-based buffer overflow happens when a program writes more data into a stack-based memory buffer than the buffer can hold. The extra data can overwrite nearby information. This is general computer-security knowledge; the article identifies the six BIG-IP flaws as stack-based buffer overflows but does not describe their technical details.

Corrupted memory can make a program behave incorrectly or crash. In some circumstances, an attacker may be able to shape the overwritten data so the program runs unintended code. F5 says these six flaws may allow remote code execution, but the source does not explain the exploit method or say that code execution has been demonstrated.

Here, the affected component is in BIG-IP’s data plane, and each flaw also requires a particular virtual-server setup. F5 says a TMM crash disrupts traffic until TMM restarts. The company has released engineering hotfixes and lists no workaround before a fix is installed. Its advisories do not report exploitation.

07

What does a load balancer or application delivery controller do as network traffic travels to online services?

In general networking terms, a load balancer or application delivery controller helps manage traffic going to online services. It can direct incoming requests among available service resources and apply traffic-handling rules. The source does not describe those functions in detail, so this explanation uses established networking knowledge.

The article’s specific example is F5 BIG-IP. Its TMM processes almost all of BIG-IP’s network traffic, and administrators use iRules to manage traffic. The critical flaws require particular iRules or an APM policy on a virtual server, showing that the affected traffic-processing setup matters.

If an attacker triggers a flaw, TMM can crash and traffic is disrupted until it restarts. F5 also says remote code execution may be possible. The management side is not exposed, according to the company, and its advisories do not report exploitation. F5 has released engineering hotfixes, but says there is no workaround until a hotfix is installed.

This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.

Read more in the JupiteX app

Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.

Or read more news on the web