A network administrator monitors a server system as a warning highlights a failed connection to the global network.
F5 has shipped out-of-band fixes for BIG-IP, and the batch is more nuanced than "patch everything now." F5 warned customers to patch six BIG-IP vulnerabilities that attackers can exploit to trigger denial-of-service (DoS) or gain remote code execution. A seventh, high-severity flaw is in the same batch. If you run BIG-IP, this is the kind of Wednesday notice that tends to ruin a Thursday.

Reading the advisories carefully matters here. Not every BIG-IP is exposed. Each bug needs a specific module, iRule command or policy to be present.

A network administrator monitors a server system as a warning highlights a failed connection to the global network. What F5 disclosed​

The six critical CVEs are CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, CVE-2026-123637, and CVE-2026-120722. They are stack-based buffer overflows affecting BIG-IP Access Policy Manager (APM) and the iRules scripting feature. F5 says unauthenticated attackers can terminate the Traffic Management Microkernel (TMM) and, on vulnerable configurations, may be able to execute code remotely.

F5 published its notification on November 18, 2026. BleepingComputer's report came two days later. The Hacker News said the notification covered 22 advisories in all, including 10 for NGINX.

F5 classifies the six critical flaws as CWE-121 stack-based buffer overflows. Each is rated CVSS 9.8 under v3.1 and 9.3 under v4.0. F5 describes them as data-plane issues with no control-plane exposure. In its words, traffic is disrupted while the TMM process restarts, and the flaw allows a remote unauthenticated attacker to cause DoS and may allow RCE.

Which configurations are at risk​

F5's advisories tie each flaw to a specific setup:

CVETrigger condition
CVE-2026-121805An iRule processing client traffic uses the PEM::subscriber command on a virtual server.
CVE-2026-120292An HTTP profile plus an iRule using MR::message route on a virtual server.
CVE-2026-120285An HTTP profile plus an iRule containing PSC::ip_address on a virtual server.
CVE-2026-116953An iRule processing client traffic uses GENERICMESSAGE::route on a virtual server.
CVE-2026-120722An iRule processing client traffic uses the DNS::scrape command on a virtual server.
CVE-2026-123637APM is provisioned, and a per-request policy with both the Client Information agent and Endpoint Security agents is applied to a virtual server.

Product scope varies by flaw. Press coverage of the notification (The Hacker News, BastionZero) says some of these also touch BIG-IP Next for Kubernetes and BIG-IP CNF. CVE-2026-123637 is described as affecting BIG-IP APM only. CVE-2026-120722 affects BIG-IP DNS. Check the advisory for each CVE rather than assuming from the product name.

F5 evaluates only versions that have not reached end of technical support. An older release that isn't listed hasn't necessarily been shown to be safe.

The separate SAML flaw: CVE-2026-126822​

This one is rated High, not Critical.

  • Cause: an integer underflow (CWE-191).
  • Condition: APM is provisioned and a virtual server has an access profile configured as a SAML Service Provider.
  • Impact: specially crafted requests can terminate TMM and cause DoS. F5's advisory does not claim RCE for this one.
  • Scores: CVSS 7.5 (v3.1) and 8.7 (v4.0).
  • Affected APM releases: 21.1.0, 17.5.0 through 17.5.1, and 17.1.0 through 17.1.3.

Unlike the critical six, this flaw has interim mitigations. You can remove the SAML Auth agent from the access policy if you don't need SAML SP. You can also restrict network access to the SAML SP virtual server to trusted client networks. Neither is a workaround for the critical flaws.

Which hotfix to install​

F5 says there is no mitigation for the six critical issues, so the fix is an engineering hotfix (EHF). Hotfix selection depends on what you already run. Canada's Cyber Centre advisory AV26-1178 lists the same fixed builds as the fix for these BIG-IP branches.

  • 21.1.x: install BIGIP-21.1.0.4.0.19.3-ENG if you are on the 21.1.0.4 base release or earlier.
  • 17.5.x: install BIGIP-17.5.1.11.0.61.12-ENG for the 17.5.1.11 base release or earlier. If you already run BIGIP-17.5.1.10.0.7.35-ENG or BIGIP-17.5.1.10.0.37.35-ENG, install BIGIP-17.5.1.10.0.80.35-ENG.
  • 17.1.x: install BIGIP-17.1.3.7.0.21.4-ENG for the 17.1.3.7 base release or earlier. If you already run BIGIP-17.1.3.6.0.9.20-ENG, install BIGIP-17.1.3.6.0.14.20-ENG.
  • Custom engineering hotfix: contact F5 Support to request a new EHF.

BIG-IP CNF has its own hotfix names. BastionZero reports CNF-2.4.2-EHF1, CNF-2.3.4-EHF1 and CNF-2.2.5-EHF1 for CVE-2026-121805 and CVE-2026-120285. BIG-IP Next for Kubernetes also has product-specific builds. Follow the matching advisory for those.

F5 distributes EHFs through MyF5 Downloads and, for some products, the F5 Artifact Repository. It cautions that EHFs don't get the full QA of scheduled releases and come with no warranty or usability guarantee. Matching the EHF to your installed version matters. A build that merely looks newer can be the wrong package.

Exposure and exploitation​

No exploitation has been reported for these CVEs. BleepingComputer says F5 hasn't flagged any of them as exploited.

The internet-exposure numbers are large. Shadowserver tracks more than 177,000 BIG-IP instances and over 14,600 IP addresses with BIG-IP APM fingerprints exposed online. Those figures show potential reach, not vulnerable systems. They don't say how many are honeypots or already patched, and a fingerprint can't show whether a vulnerable iRule or policy is configured.

The urgency comes from history, not from evidence about these CVEs. CISA has flagged seven F5 vulnerabilities as actively exploited since November 2021, four of them also used by ransomware gangs. In September, F5 patched a critical BIG-IP APM vulnerability (CVE-2026-94127) that is being actively exploited in zero-day RCE attacks. BleepingComputer also notes F5's disclosure a year ago that state-backed hackers had stolen BIG-IP source code and details of undisclosed vulnerabilities. That raises the stakes for any bug in this product line. It isn't proof that these flaws were known to attackers.

A practical checklist​

  • Inventory your BIG-IP estate. Note the version, the provisioned modules (especially APM and PEM), and any hotfixes already installed.
  • Search your iRules for PEM::subscriber, MR::message route, PSC::ip_address, GENERICMESSAGE::route and DNS::scrape. Note which virtual servers use them, and whether those also have HTTP profiles.
  • Review APM per-request policies for the Client Information agent combined with Endpoint Security agents. Also look for SAML SP access profiles.
  • Prioritize internet-facing virtual servers. Because these are data-plane bugs, any virtual server that processes untrusted traffic matters most.
  • Pick the right EHF from F5's version-specific guidance, and test it in a staging pair if you can.
  • Plan for a TMM restart. Use a high-availability pair, failover, and a maintenance window. TMM is exactly what the attacks crash, and installs can cause brief disruption too.
  • Watch for crashes. Unexpected TMM restarts or core files are worth investigating before and after patching.
  • Re-check F5's advisories. Disclosures like this are sometimes updated after publication, and scope can change.

Why Windows and enterprise admins should care​

BIG-IP often sits in front of Exchange, SharePoint, VDI and SAML-based single sign-on. It often does so as a reverse proxy or an APM gateway. A crashed TMM can take down those front doors. If an attacker did get code execution, a device at the network edge would be an attractive pivot point. That is general industry context, not a claim from F5's advisories.

The caveat is that configuration-dependent flaws can be less widespread than the headline suggests. But "specific conditions" has a way of describing production setups, not edge cases. APM is common, and so are iRules that grew organically over a decade. Check your own estate rather than assuming you're not affected.

Bottom line​

Six critical, configuration-dependent stack overflows can crash TMM and may enable RCE. They have no mitigation, and only hotfixes address them. A seventh, high-severity SAML flaw causes DoS and has two interim mitigations. No active exploitation has been reported yet. With BIG-IP's exploitation history, treat the patch window as short.


Correction (November 20, 2026): An earlier version of this article said F5 disclosed five critical BIG-IP flaws. F5's November 18 notification actually lists six: CVE-2026-120722, a stack-based buffer overflow triggered by an iRule using the DNS::scrape command on BIG-IP DNS, was missing. The count, CVE list, trigger table and iRule checklist have been corrected.

 

References

  1. F5 releases emergency patches for critical BIG-IP RCE flaws BleepingComputer 2026-11-20T05:57:43-05:00
  2. F5 BIG-IP Critical Flaws Crash TMM, May Allow RCE bastionzero.com
  3. F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE thehackernews.com