Skip to main content
All incident reports
Incident report

F5 discloses six critical BIG-IP flaws that can crash traffic and may allow remote code execution

F5 published advisories on 18 November for six critical stack-based buffer overflows in BIG-IP's data plane, each of which needs a specific virtual-server configuration to be reachable. Fixes exist only as engineering hotfixes, and F5 lists no workaround.

· First published

The short version

  • The flaws. Six critical vulnerabilities in BIG-IP let an unauthenticated attacker crash the Traffic Management Microkernel (TMM), the component that handles most of the product's network traffic, until it restarts. F5 says they may also allow remote code execution. All six are rated 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0.
  • Narrow conditions. Each flaw is reachable only where a virtual server is set up in a particular way: an iRule that uses a named command, or in one case an APM per-request policy containing both Client Information and Endpoint Security agents. Five of the six are in iRules. F5 says the management interface is not exposed.
  • Fixes and caveats. F5 has released engineering hotfixes, builds issued between scheduled releases, and states there is no workaround before one is installed. Its policy warns that such hotfixes do not receive the same QA assessment as scheduled releases and come with no warranty.
  • Discovery and exploitation. WatchTowr researcher Sina Kheirkhah reported four of the flaws and F5 found the other two. None of the advisories says any of the six has been exploited. Some also affect BIG-IP Next for Kubernetes and BIG-IP CNF.
  • Wider advisory batch. The six arrived among 22 advisories F5 published that day, ten of them for NGINX, together with six lower-rated BIG-IP and BIG-IQ flaws covering iControl SOAP and REST and several APM denial-of-service issues.

Timeline

DateEvent
22 SeptemberF5 discloses CVE-2026-94127, a heap-based buffer overflow in APM setups acting as OAuth authorisation servers, which was later exploited and added by CISA to its Known Exploited Vulnerabilities catalogue.
18 NovemberF5 publishes 22 advisories, including six critical data-plane flaws in BIG-IP for which it releases engineering hotfixes only.

What the flaws allow

The six are stack-based buffer overflows in BIG-IP's data plane. An attacker who can reach a suitably configured virtual server can crash TMM without logging in, cutting traffic until the process restarts. F5 says the same flaws may allow remote code execution.

Reachability depends on configuration rather than on exposure alone. Five of the flaws sit in iRules, the scripting feature administrators use to steer traffic, and require an iRule that calls a specific command such as PEM::subscriber, MR::message route, PSC::ip_address, GENERICMESSAGE::route or DNS::scrape. The sixth needs an APM per-request policy that includes both Client Information agents and Endpoint Security agents.

Which systems are affected and how to fix them

Beyond on-premises BIG-IP, the flaws reach some cloud-native editions. BIG-IP Next for Kubernetes is affected by five of the six and BIG-IP CNF by two of them according to the advisory, though the CVE record for CVE-2026-120722 lists CNF as affected as well. BIG-IP Next for Kubernetes is fixed in BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 and BNK-2.2.5-EHF1, for versions 2.4.0 to 2.4.2, 2.3.0 to 2.3.4 and 2.2.0 to 2.2.5; the advisories list matching CNF builds for CVE-2026-121805 and CVE-2026-120285.

For the six critical flaws, the only remedy is an engineering hotfix obtained through F5 support. The company warns that "engineering hotfixes do not undergo the extensive QA assessment of scheduled software releases." A system already running a custom hotfix needs a new one from support rather than the published build.

There is a gap for older deployments. F5 checks only releases still inside technical support, so a version missing from its tables has not been shown to be safe.

The rest of the batch and earlier exploitation

The same publication round covers six lower-rated flaws. The highest, at 8.8, is an iControl SOAP issue that lets a user with at least the Guest role send unauthorised management requests, potentially running system commands or disabling services; access to iControl SOAP should be limited to trusted networks until the listed builds are installed. Another flaw means iControl REST tokens may not expire as expected, and an attacker who already holds a token may be able to extend how long it stays valid unless its owner deletes it.

This set differs from CVE-2026-94127, an APM heap overflow disclosed on 22 September that was later exploited and that CISA added to its Known Exploited Vulnerabilities catalogue. That flaw needed different settings.

What is not known yet

  • Whether any of the six critical flaws has been exploited in the wild; the advisories do not say.
  • What conditions beyond the described configuration would be needed for an attacker to achieve remote code execution rather than only a crash.
  • How many BIG-IP deployments actually use the iRule commands or the APM agent combination the flaws require.
  • Whether CVE-2026-120722 affects BIG-IP CNF: F5's advisory lists CNF as not vulnerable while its CVE record, updated the same day, lists it as affected.
  • Whether BIG-IP releases outside technical support are affected, since F5 checked only supported versions.

What to do

If you run BIG-IP, BIG-IP Next for Kubernetes or BIG-IP CNF

  1. Inventory virtual servers with iRules that call PEM::subscriber, MR::message route, PSC::ip_address, GENERICMESSAGE::route or DNS::scrape, and any APM per-request policy that combines Client Information and Endpoint Security agents.
  2. Request the engineering hotfix from F5 support for each affected version, and ask for a new hotfix if you already run a custom one.
  3. Apply the fixes for the APM and SAML denial-of-service flaws, which share the same hotfixes, or remove the SAML auth agent and restrict those virtual servers to trusted networks in the meantime.
  4. For the iControl SOAP flaw, restrict iControl SOAP access to trusted networks until the listed BIG-IP or BIG-IQ build is installed, checking first that blocking it on self-IP addresses will not break high-availability pairs.

If you operate token-based automation against BIG-IP

  1. Change token-creating scripts to delete iControl REST tokens once they are no longer needed, rather than relying on expiry.

For everyone else

  1. Do not treat a release's absence from a vendor's fixed-version tables as evidence that it is unaffected; confirm support status with the vendor directly.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

We email you about this topic only; unsubscribe any time. See our Privacy Policy.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.