SecureCyberVM
CVE Lookup Daily Threat Briefing Exploited CVEs Ransomware Zero-day
SecureCyberVM
Get the Patch Brief

F5 ships emergency hotfixes for critical BIG-IP TMM flaws that may allow RCE

F5 has released out-of-band engineering hotfixes for critical stack-based buffer overflows in BIG-IP that let unauthenticated attackers crash the Traffic Management Microkernel and may allow remote code execution. No workaround exists.

F5 ships emergency hotfixes for critical BIG-IP TMM flaws that may allow RCE

F5 has released out-of-band engineering hotfixes for a group of critical vulnerabilities in BIG-IP that allow an unauthenticated remote attacker to crash the Traffic Management Microkernel (TMM), the data-plane component that handles application traffic. According to F5’s advisories, as reported by BleepingComputer and The Hacker News, the flaws may also allow remote code execution on systems with the affected configurations.

The vendor has not listed any mitigation that removes the risk short of installing the hotfixes, and engineering hotfixes are not part of a scheduled release. None of the advisories describes the flaws as exploited in attacks, but F5 BIG-IP appliances have been a repeated target for both state-backed and ransomware operators, which raises the urgency for exposed deployments.

What happened

F5 published a batch of security advisories this week. The Hacker News reported that the release included 22 advisories, 10 of them for NGINX, and that six BIG-IP flaws were rated critical. All six are described as stack-based buffer overflows in the data plane; F5 stated that the control plane is not exposed. BleepingComputer, reporting on Friday, described five of these as critical flaws affecting BIG-IP Access Policy Manager (APM) and the iRules feature, alongside a high-severity APM SAML issue.

Each critical flaw is reachable only when a virtual server uses a specific configuration, according to The Hacker News:

CVETriggering configurationProducts named
CVE-2026-123637APM per-request policy with both the Client Information and Endpoint Security agentsBIG-IP APM
CVE-2026-121805iRule using PEM::subscriber on client trafficBIG-IP PEM, BIG-IP Next for Kubernetes, BIG-IP CNF
CVE-2026-120292HTTP profile plus iRule using MR::message routeBIG-IP (all modules), BIG-IP Next for Kubernetes
CVE-2026-120285HTTP profile plus iRule using PSC::ip_addressBIG-IP (all modules), BIG-IP Next for Kubernetes, BIG-IP CNF
CVE-2026-116953iRule using GENERICMESSAGE::route on client trafficBIG-IP (all modules), BIG-IP Next for Kubernetes
CVE-2026-120722iRule using DNS::scrape on client trafficBIG-IP DNS, BIG-IP Next for Kubernetes

The same release includes lower-rated issues. These include CVE-2026-126822, an integer underflow in APM when an access profile acts as a SAML Service Provider, and CVE-2026-125272, a TMM crash tied to a form-based Logon Page in a per-request policy. Both are fixed in the same engineering hotfixes. The Hacker News also reported CVE-2026-126336 (APM SAML with encrypted assertions), CVE-2026-121812 (APM and SSL Orchestrator with a non-default policy trace key enabled), CVE-2026-125274 (iControl SOAP access by low-privileged users) and CVE-2026-120718 (iControl REST tokens that may not expire as expected).

Who is affected

Organizations running BIG-IP with APM, PEM or DNS, or with iRules that call the listed commands on client traffic, are in scope, as are BIG-IP Next for Kubernetes deployments on the 2.2, 2.3 and 2.4 branches. The Hacker News reported fixed builds for BIG-IP Next for Kubernetes as BNK-2.4.2-EHF1, BNK-2.3.4-EHF1 and BNK-2.2.5-EHF1, with matching CNF hotfixes for two of the flaws. Specific hotfix build names for classic BIG-IP were not given in either report; administrators should take them from F5’s advisories. F5 notes that it evaluates only versions still under technical support, so older releases absent from its tables should not be assumed safe.

The sources conflict on one point: F5’s advisory for CVE-2026-120722 lists BIG-IP CNF as not vulnerable, while the CVE record lists it as affected, according to The Hacker News.

Severity and exploitation

F5 rates the six flaws critical, and The Hacker News reported identical scores for all of them. Exploitation requires no authentication but depends on the vulnerable configuration being present. F5 has not flagged any of the issues as exploited, according to BleepingComputer. The outlet cited Shadowserver data showing more than 177,000 BIG-IP instances and over 14,600 IP addresses with BIG-IP APM fingerprints exposed online, though it is unclear how many are honeypots or already patched. BleepingComputer also noted that CISA has listed seven F5 flaws as exploited since November 2021, and that F5 patched an exploited APM remote code execution flaw, CVE-2026-94127, in September.

What defenders should do now

  1. Inventory BIG-IP, BIG-IP Next for Kubernetes and CNF systems, and identify virtual servers that use APM per-request policies, SAML Service Provider profiles, or iRules calling PEM::subscriber, MR::message, PSC::ip_address, GENERICMESSAGE::route or DNS::scrape.
  2. Obtain and install the engineering hotfixes referenced in F5’s advisories for affected configurations, prioritizing internet-facing APM and iRules deployments. Plan for traffic disruption while TMM restarts.
  3. Systems already running a custom engineering hotfix need a new build from F5 support, according to F5’s hotfix policy as cited by The Hacker News.
  4. Where the SAML Service Provider function is not needed, remove the SAML Auth agent and limit access to trusted client networks, as F5 advised for CVE-2026-126822.
  5. Restrict iControl SOAP and REST management interfaces to trusted networks and delete iControl REST tokens when no longer needed.
  6. Monitor for unexpected TMM restarts or crashes, which may indicate attempted exploitation.

SCVM analysis

The configuration requirements narrow the exposure, but iRules and APM are core to how many organizations use BIG-IP, so the affected population is likely to be broad. The bigger operational problem is the remedy: engineering hotfixes carry less QA than scheduled releases and come without a workaround, leaving teams to choose between untested builds and running exposed. Given the history of rapid weaponization of BIG-IP flaws and F5’s 2025 disclosure that attackers stole information on undisclosed BIG-IP vulnerabilities, defenders should treat these as likely future targets and patch internet-facing systems first, ideally using high-availability pairs to absorb restarts.

Sources

About this article: produced by the SCVM Newsroom with AI assistance from the public sources linked above, enriched with NVD, FIRST EPSS and CISA KEV data, and checked by automated quality controls under our editorial policy. Spotted an error? Request a correction.

SecureCyberVM

Install SecureCyberVM

Get the Daily Threat Briefing and exploited-CVE alerts one tap away, full screen, like an app.