Security Digest · Nov 18, 2026 · Vulnerability · Network edge

F5 BIG-IP: Six Critical iRule and APM Overflows Hotfixed

Six 9.8-rated BIG-IP flaws let unauthenticated attackers crash TMM and maybe run code, but only with specific iRules or APM policies. Hotfixes only.

Our verdict

Check exposure

Search your iRules and APM per-request policies today; if any virtual server matches one of the six named configurations, install F5's engineering hotfix this week, because F5 lists no workaround and attackers have moved fast on BIG-IP bugs before.

Who must act: BIG-IP 17.1, 17.5 and 21.1 and BIG-IP Next for Kubernetes or CNF administrators whose virtual servers run iRules using PEM::subscriber, MR::message route, PSC::ip_address, GENERICMESSAGE::route or DNS::scrape, or APM per-request policies with Client Information and Endpoint Security agents.

Who can relax: BIG-IP sites that use none of those iRule commands or APM agent combinations: the critical flaws do not reach them, the management plane is not exposed, and only the lower-rated APM crash bugs may still apply.

Affected
BIG-IP 21.1.x before BIGIP-21.1.0.4.0.19.3-ENG
BIG-IP 17.5.x before BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG
BIG-IP 17.1.x before BIGIP-17.1.3.7.0.21.4-ENG or BIGIP-17.1.3.6.0.14.20-ENG
BIG-IP Next for Kubernetes 2.2.0 to 2.2.5, 2.3.0 to 2.3.4 and 2.4.0 to 2.4.2
BIG-IP Next CNF 2.2.0 to 2.4.2 (some of the iRule flaws)
Only when a virtual server uses one of the vulnerable iRule commands or APM policy configurations
Fixed in
BIGIP-21.1.0.4.0.19.3-ENG
BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG
BIGIP-17.1.3.7.0.21.4-ENG or BIGIP-17.1.3.6.0.14.20-ENG
BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1
CNF-2.4.2-EHF1, CNF-2.3.4-EHF1, CNF-2.2.5-EHF1
CVSS
9.8 (v3.1, vendor)
EPSS
0.8% (percentile 57)
CISA KEV
Not listed
Exploitation
No known exploitation
Severity
Critical

What to do

  1. Record the version and provisioned modules on every BIG-IP, standby units included, with tmsh show sys version and tmsh list sys provision.
  2. Search all partitions for the vulnerable iRule commands with grep -nE 'PEM::subscriber|MR::message +route|PSC::ip_address|GENERICMESSAGE::route|DNS::scrape' /config/bigip.conf /config/partitions/*/bigip.conf.
  3. On APM systems, check every per-request policy for a Client Information agent combined with Endpoint Security agents, and list SAML SP access profiles and per-request policies with a form-based Logon Page.
  4. Where anything matches, install the engineering hotfix for your branch this week, standby unit first, following F5's K000164239 guidance; ask F5 support for a rebuilt hotfix if you already run a custom one.
  5. Until patched, remove or rewrite matching iRules where the business allows; F5 lists no workaround for the six critical flaws.
  6. For the SAML SP crash, remove the SAML Auth agent if SAML SP is not needed, or limit that virtual server to trusted client networks.

How to check if you are affected or compromised

  • Review /var/log/ltm for unexpected TMM restarts and HA failovers since November 18, 2026, and check /var/core for new TMM core files.
  • Correlate any crash with traffic to virtual servers that carry the affected iRules or APM policies.
  • F5 has published no indicators of compromise; a crash-free log does not prove that a code-execution attempt failed.
  • If you find unexplained TMM crashes on a matching configuration, collect a qkview and open an F5 case before rebuilding.

What happened#

On November 18, 2026, F5 published an out-of-band security notification with 22 advisories across BIG-IP, BIG-IQ and NGINX, according to The Hacker News. Six of the flaws are rated critical, 9.8 under CVSS 3.1 and 9.3 under CVSS 4.0. All six are stack-based buffer overflows in the Traffic Management Microkernel (TMM), which handles BIG-IP's data plane. F5's CVE records say that "undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE)," and that the attacker needs no credentials. They add: "There is no control plane exposure; this is a data plane issue only." The only fixes are engineering hotfixes, and each critical record lists the workaround as "None".

Each flaw needs a specific configuration on a virtual server:

  • CVE-2026-123637: BIG-IP APM with a per-request policy that includes the Client Information agent and Endpoint Security agents.
  • CVE-2026-121805: an iRule using PEM::subscriber on client traffic.
  • CVE-2026-120292: an HTTP profile plus an iRule using MR::message route.
  • CVE-2026-120285: an HTTP profile plus an iRule using PSC::ip_address.
  • CVE-2026-116953: an iRule using GENERICMESSAGE::route on client traffic.
  • CVE-2026-120722: an iRule using DNS::scrape on client traffic.

The same hotfixes also fix two high-severity (7.5) crash bugs in APM that need no login: CVE-2026-126822, when an access profile acts as a SAML Service Provider, and CVE-2026-125272, when a per-request policy contains a form-based Logon Page. BleepingComputer counted five critical flaws; the sixth, DNS::scrape, is in its CVE record and the Canadian Centre for Cyber Security alert.

Who is affected#

The CVE records list BIG-IP 17.1.x, 17.5.x and 21.1.x. The Hacker News reports that three of the iRule flaws affect all modules, while the others are limited to PEM, BIG-IP DNS or APM. F5's hotfix guidance says which build fits which starting point. BIG-IP Next for Kubernetes and, for some of the flaws, BIG-IP Next CNF need their own EHF1 builds. F5 does not evaluate releases past End of Technical Support, so an older branch missing from its tables has not been shown to be safe.

BleepingComputer cites Shadowserver counts of more than 177,000 BIG-IP instances and over 14,600 IP addresses with APM fingerprints online. How many of them run the vulnerable configurations had not been disclosed as of Nov 21, 2026.

Do you really need to act?#

Only if your configuration matches, but check today. None of these bugs is reachable in a default setup. Several of the named commands belong to specialized features, such as PEM subscriber handling, message routing and DNS, so a BIG-IP with only ordinary HTTP iRules is unlikely to match. On a configuration that does match, an attacker needs no credentials. CISA's scoring in each record rates the flaws automatable with total technical impact, but records no exploitation. F5 has not reported exploitation, and no public exploit had been disclosed as of Nov 21, 2026. Per The Hacker News, watchTowr's Sina Kheirkhah reported four of the flaws.

History is a reason not to wait. APM flaw CVE-2026-94127, disclosed on September 22, was exploited, and CISA added it to its KEV catalog the same day, The Hacker News reports. The hotfixes carry some risk: The Hacker News quotes F5's warning that they "do not undergo the extensive QA assessment of scheduled software releases." Install them in a maintenance window using HA failover.

What to do now#

  1. Record the version and modules on every unit, standby units included: tmsh show sys version and tmsh list sys provision.
  2. Search every partition for the vulnerable commands: grep -nE 'PEM::subscriber|MR::message +route|PSC::ip_address|GENERICMESSAGE::route|DNS::scrape' /config/bigip.conf /config/partitions/*/bigip.conf, then map any matching rule to its virtual servers.
  3. On APM systems, check every per-request policy for a Client Information agent combined with Endpoint Security agents. Also list SAML SP access profiles and per-request policies with a form-based Logon Page.
  4. Where anything matches, install the hotfix for your branch this week, standby unit first. If you already run a custom engineering hotfix, ask F5 support for a rebuilt one.
  5. Until then, remove or rewrite matching iRules where the business allows. This lowers risk, but F5 does not list it as a workaround. For CVE-2026-126822, F5 suggests removing the SAML Auth agent if SAML SP is not needed, or limiting that virtual server to trusted client networks.
  6. Read the rest of the notification, which includes iControl and NGINX fixes.

How to tell if you were hit#

A failed attempt most likely shows up as a TMM crash and, on an HA pair, a failover. Review /var/log/ltm for unexpected TMM restarts since November 18, check /var/core for new TMM core files, and compare any crash with traffic to the affected virtual servers. F5 had published no indicators of compromise as of Nov 21, 2026. A successful code-execution exploit need not crash anything, so a quiet log proves nothing. If you find unexplained crashes on a matching configuration, collect a qkview and open an F5 case before you rebuild.

Timeline#

  • — F5 discloses APM flaw CVE-2026-94127, later exploited; CISA adds it to KEV.
  • — F5 publishes the out-of-band notification, 22 advisories and engineering hotfixes; the CVE records for the six critical flaws go live.
  • — The Canadian Centre for Cyber Security issues AV26-1178.
  • — BleepingComputer reports the hotfixes; F5 has not flagged exploitation.

Vulnerability records

  • CVE-2026-123637 · When BIG-IP APM is provisioned and a per-request policy that includes the Client Information agent and Endpoint Security agents is applied to a virtual…
  • CVE-2026-121805 · Description: When an iRule that processes client traffic using the PEM::subscriber command is configured on a virtual server, undisclosed requests can cause…
  • CVE-2026-120292 · Description: When an HTTP profile and an iRule using the MR::message route command are configured on a virtual server, undisclosed requests can cause the…
  • CVE-2026-120285 · Description When an HTTP profile and an iRule containing the PSC::ip_address command are configured on a virtual server, undisclosed requests can cause the…
  • CVE-2026-116953 · Description: When an iRule that processes client traffic using the GENERICMESSAGE::route command is configured on a virtual server, undisclosed requests can…
  • CVE-2026-120722 · Description: When an iRule that processes client traffic using the DNS::scrape command is configured on a virtual server, undisclosed requests can cause the…
  • CVE-2026-126822 · Description: When BIG-IP APM is provisioned, an Access Profile is configured as a SAML SP (Service Provider) and is applied to a virtual server, undisclosed…
  • CVE-2026-125272 · Description: When BIG-IP APM is licensed and provisioned, and a virtual server with the APM access profile is configured with a per-request policy containing…

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. F5 — Out-of-band Security Notification (November 18, 2026), K000164058 my.f5.com
  2. F5 — Special considerations for engineering hotfixes released on November 18, 2026, K000164239 my.f5.com
  3. F5 — K000163937: BIG-IP APM vulnerability CVE-2026-123637 my.f5.com
  4. F5 — K000163946: BIG-IP iRule vulnerability CVE-2026-121805 my.f5.com
  5. F5 — K000163940: BIG-IP iRule vulnerability CVE-2026-120292 my.f5.com
  6. F5 — K000163939: BIG-IP iRule vulnerability CVE-2026-120285 my.f5.com
  7. F5 — K000163941: BIG-IP iRule vulnerability CVE-2026-116953 my.f5.com
  8. F5 — K000163945: BIG-IP iRule vulnerability CVE-2026-120722 my.f5.com
  9. F5 — K000163942: BIG-IP APM SAML vulnerability CVE-2026-126822 my.f5.com
  10. F5 — K000163938: BIG-IP APM vulnerability CVE-2026-125272 my.f5.com
  11. CVE record — CVE-2026-123637 cve.org
  12. CVE record — CVE-2026-120722 cve.org
  13. CVE record — CVE-2026-126822 cve.org
  14. Canadian Centre for Cyber Security — F5 security advisory (AV26-1178) cyber.gc.ca

Coverage and analysis

  1. The Hacker News — F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE thehackernews.com
  2. BleepingComputer — F5 releases emergency patches for critical BIG-IP RCE flaws bleepingcomputer.com