Research

F5's Six Critical BIG-IP Flaws Each Need a Specific iRule or APM Policy to Bite. How to Tell in Five Minutes Whether Your Config Is in Scope

F5's Six Critical BIG-IP Flaws Each Need a Specific iRule or APM Policy to Bite. How to Tell in Five Minutes Whether Your Config Is in Scope

If you run F5 BIG-IP, do not panic over "six critical." Run one command first: search your iRules for five command names (the list is below). If none of them appears in an iRule attached to a virtual server, and you don't run an APM per-request policy with the Client Information and Endpoint Security agents, none of the six critical flaws F5 disclosed on Wednesday, November 18 applies to your box. If one does, that virtual server is exposed to an unauthenticated attacker who can crash it and may be able to run code. Get the engineering hotfix from F5 support today.

The six, and the one condition each needs

All six are stack-based buffer overflows (CWE-121) in the Traffic Management Microkernel (TMM), the data plane that carries your traffic. F5 rates each 9.8 under CVSS 3.1 and 9.3 under CVSS 4.0. Each is unauthenticated over the network. F5's wording is the same for all six: undisclosed requests "can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE)." F5 also says each is "a data plane issue only," with no exposure of the management interface.

The score assumes the vulnerable configuration exists. Most of these are opt-in iRule commands that a default BIG-IP does not use.

  • CVE-2026-123637 (F5 article K000163937). In scope only if APM is provisioned AND a per-request policy that contains BOTH the Client Information agent and Endpoint Security agents is applied to a virtual server. BIG-IP only. Reported by Sina Kheirkhah of watchTowr.
  • CVE-2026-121805 (K000163946). In scope if an iRule that processes client traffic uses PEM::subscriber on a virtual server. Module: PEM (Policy Enforcement Manager). Also listed for BIG-IP Next for Kubernetes and BIG-IP Next CNF. Found by F5.
  • CVE-2026-120292 (K000163940). In scope if a virtual server has BOTH an HTTP profile AND an iRule using MR::message route. Any module. Also BIG-IP Next for Kubernetes. Reported by watchTowr.
  • CVE-2026-120285 (K000163939). In scope if a virtual server has BOTH an HTTP profile AND an iRule containing PSC::ip_address. F5's record names PEM. Also BIG-IP Next for Kubernetes and BIG-IP Next CNF. Reported by watchTowr.
  • CVE-2026-116953 (K000163941). In scope if an iRule that processes client traffic uses GENERICMESSAGE::route. Any module. Also BIG-IP Next for Kubernetes. Reported by watchTowr.
  • CVE-2026-120722 (K000163945). In scope if an iRule that processes client traffic uses DNS::scrape. Module: DNS. Also BIG-IP Next for Kubernetes and BIG-IP Next CNF. Found by F5.

Affected BIG-IP branches in F5's records: 21.1.x, 17.5.x and 17.1.x. BIG-IP Next for Kubernetes and CNF: 2.2.x, 2.3.x and 2.4.x. F5 notes that versions past End of Technical Support "are not evaluated," so an older box is unknown, not safe.

Am I affected? Five minutes, from the shell

Run these from the BIG-IP command line (bash, or prefix with tmsh where shown).

  1. Which version are you on? Run "tmsh show sys version". Anything on 21.1, 17.5 or 17.1 without the November engineering hotfix is in the affected range. Older than 17.1 was not evaluated.
  2. Search every iRule in every partition for the five commands. Run tmsh -q -c "cd /; list ltm rule recursive" and pipe it through grep -E "PEM::subscriber|MR::message|PSC::ip_address|GENERICMESSAGE::route|DNS::scrape". No output means none of the five iRule-based CVEs applies. Note the rule names of any match.
  3. Is that rule attached to a virtual server? Run tmsh -q -c "cd /; list ltm virtual recursive one-line" and grep for each rule name from step 2. An unattached rule is not in scope. For MR::message and PSC::ip_address, also confirm the same virtual server has an HTTP profile (look for "http" in the profiles list on that line).
  4. Is APM provisioned? Run "tmsh list sys provision" and look for apm at a level other than none. If it is, open Access, then Profiles / Policies, then Per-Request Policies in the web UI, and check whether any per-request policy contains BOTH a Client Information agent and an Endpoint Security agent and is attached to a virtual server. That is the only configuration F5 names for CVE-2026-123637.
  5. Already crashing? A TMM crash leaves a restart in /var/log/ltm and usually a core file in /shared/core. Run grep -i "tmm" /var/log/ltm | grep -iE "restart|core|exit" and list /shared/core. Unexplained TMM restarts on a virtual server from steps 2 to 4 are worth a ticket with F5.

What to do if you are in scope

  1. Open a case with F5 support for the engineering hotfix. F5's records list engineering hotfix builds, not a regular maintenance release, as the fix: BIGIP-21.1.0.4.0.19.3-ENG on 21.1; BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG on 17.5; BIGIP-17.1.3.7.0.21.4-ENG or BIGIP-17.1.3.6.0.14.20-ENG on 17.1. For BIG-IP Next for Kubernetes and CNF, the fixes are 2.4.2-EHF1, 2.3.4-EHF1 and 2.2.5-EHF1. F5 warns that engineering hotfixes "do not undergo the extensive QA assessment of scheduled software releases" (as quoted by The Hacker News), and a box already running a custom hotfix needs a new one built by support. Test before you roll.
  2. Until then, take the command out of the path if you can. F5 lists no workaround for the six (per The Hacker News). This step is our suggestion, not F5's: if an iRule only uses the vulnerable command for something you can live without for a few days, detach the rule or rewrite that branch. If the rule is your routing logic, you can't, and the hotfix is the only fix.
  3. Run HA. Each flaw at minimum crashes TMM, and traffic stops while it restarts. A device group with failover turns an outage into a blip while you patch.
  4. Patch the control plane too, separately. The same release fixes CVE-2026-125274 (CVSS 8.8): any iControl SOAP user with the Guest role or higher can inject a management request that may run system commands. F5's record says it is fixed in BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6, and BIG-IQ 8.4.2.3, as regular releases. If your management interface is reachable by anyone but your admins, this is the one to schedule first, even though it scores lower.

The lower-rated six, briefly

Four more TMM crashes in APM (CVSS 7.5 each), each again tied to a configuration: CVE-2026-125272 (per-request policy with a form-based Logon Page), CVE-2026-126822 (access profile acting as a SAML Service Provider), CVE-2026-126336 (SAML SP agent with encrypted assertions; The Hacker News reports fixes in 21.1.0.3, 17.5.1.10 and 17.1.3.6, but F5's CVE record lists no fixed version, so confirm with F5), and CVE-2026-121812 (only when the tmm.access.policytrace database key is enabled; it is off by default, check with "tmsh list sys db tmm.access.policytrace"). CVE-2026-120718 (8.1): iControl REST tokens may not expire as they should, fixed in 21.1.0.2, 17.5.1.10 and 17.1.3.6. Plus the iControl SOAP flaw above.

Is any of it being exploited?

Not that anyone has said. Neither F5's CVE records nor CISA's Known Exploited Vulnerabilities catalog (the JSON released November 18 at 19:17 UTC) lists any of the twelve as exploited. The Hacker News, which read F5's advisories, reports that none of them says so. Do not confuse this batch with CVE-2026-94127, a separate APM heap overflow that CISA added to KEV on Tuesday, September 22, with a September 25 due date. If you have not patched that one, it comes first.

No indicators of compromise were published in the sources we read, so we added nothing to our feed.

What our edge saw

These are data-plane bugs reached through "undisclosed requests" on your own virtual servers, with no published request path, and no public proof-of-concept had been harvested by our PoC tracker when we checked. Our edge has no fingerprint to match, so we cannot tell you whether anyone is probing for them. For context only: since October 19 our edge blocked 514,113 requests, and one (November 7, a curl spray from AS211590) probed a BIG-IP management path, the old /tmui/ traversal from CVE-2020-5902. That is recon against a six-year-old management-plane bug, not a sighting of anything in this release. We don't run BIG-IP.

Some details still disagree

  • The Hacker News reports that F5's advisory for CVE-2026-120722 lists BIG-IP Next CNF as not vulnerable, while the CVE record, updated the same day, lists CNF as affected. If you run CNF with DNS::scrape, treat it as affected.
  • F5's CVE record for CVE-2026-121805 (PEM::subscriber) labels its Kubernetes and CNF entries with the module "DNS::scrape." That looks like a copy error in the record. The command that matters for that CVE is PEM::subscriber.

How we know

F5 is the CVE numbering authority for its own products, so we read F5's six CVE records directly from the CVE Program's API (all published November 18 at 15:23 UTC). They give each description, CVSS vectors, affected branches, hotfix build names, the K-article number and the credit. F5's K-articles on my.f5.com did not load for our reader: the pages render in the browser and returned only a loading shell. The notification number (K000164058), the hotfix QA quote, the "no workaround" statement and the exploitation read come from The Hacker News, which is one report of F5's advisories, not independent confirmation. We checked the KEV catalog JSON for all twelve CVE ids and found none of them listed.

Sources

  • F5 CVE records on CVE.org: CVE-2026-123637, CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, CVE-2026-120722, CVE-2026-125274, CVE-2026-120718, CVE-2026-125272, CVE-2026-126822, CVE-2026-126336, CVE-2026-121812, published November 18, 2026.
  • F5 Security Notification K000164058, my.f5.com/manage/s/article/K000164058 (did not render for our reader), and the per-CVE K-articles K000163937, K000163946, K000163940, K000163939, K000163941 and K000163945.
  • F5 hotfix policy, K4918.
  • The Hacker News, "F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE," November 18, 2026.
  • CISA Known Exploited Vulnerabilities catalog JSON, version 2026.11.18.

Read next: F5's 2025 Breach From the Primary Sources: What Was Taken and What to Check on Your Devices


How do AI models see YOUR brand?

AIPM has audited 250+ domains. 15 seconds. Free while still in beta.

Audit your site now → aipmsec.com


Was this useful? Thirty seconds, no cookies, no tracking, no third parties, your address hashed and never stored. The question lives here: https://analytics.dugganusa.com/nps.html#post=f5-big-ip-six-critical-irule-config-triage