Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Security News

Six F5 BIG-IP iRule and APM Flaws: Configuration and Patch Decisions

F5 BIG-IP iRule vulnerabilities: compare six conditional TMM flaws, affected virtual-server configurations, and exact hotfix builds to verify.

Published Reading Time5 Min Read
Edge appliance traffic dividing into configuration paths, with one highlighted path

F5 BIG-IP iRule vulnerabilities disclosed on November 18, 2026, have six different configuration triggers. Five concern client traffic handled by an iRule command. The sixth requires a specific BIG-IP APM per-request policy, so an inventory of CVE numbers alone will not identify the exposed virtual servers.

F5’s CVE records say crafted, undisclosed requests can terminate the Traffic Management Microkernel (TMM), interrupting traffic while it restarts. Remote code execution is a possible further outcome, not a documented outcome of an observed attack. The records describe data plane exposure and explicitly exclude control plane exposure.

CVEBIG-IPNext KubernetesNext CNF
CVE-2026-116953AffectedAffectedUnknown
CVE-2026-120285AffectedAffectedAffected
CVE-2026-120292AffectedAffectedUnknown
CVE-2026-120722AffectedAffectedAffected
CVE-2026-121805AffectedAffectedcheck module labelAffectedcheck module label
CVE-2026-123637AffectedUnknownUnknown
  • Affected
  • Unknown

“Affected” means the product appears in F5’s affected-version data, subject to the configuration condition below. “Unknown” means that record does not list the product, not that the product is proven safe. The two Next entries for CVE-2026-121805 need vendor confirmation because their module labels conflict with that record’s PEM::subscriber description.

Which F5 BIG-IP iRule Vulnerabilities Match Your Configuration?

CVE Required virtual-server condition Product scope in F5’s record
CVE-2026-116953 Client-traffic iRule using GENERICMESSAGE::route BIG-IP; Next for Kubernetes
CVE-2026-120285 HTTP profile and iRule containing PSC::ip_address BIG-IP; Next for Kubernetes; Next CNF
CVE-2026-120292 HTTP profile and iRule using MR::message route BIG-IP; Next for Kubernetes
CVE-2026-120722 Client-traffic iRule using DNS::scrape BIG-IP; Next for Kubernetes; Next CNF
CVE-2026-121805 Client-traffic iRule using PEM::subscriber BIG-IP; Next products listed with a conflicting module label
CVE-2026-123637 Provisioned APM and per-request policy with Client Information and Endpoint Security agents BIG-IP only in the record

The first five rows are command-specific, while CVE-2026-123637 depends on APM policy composition. A virtual server with an HTTP profile alone does not meet the two HTTP-profile conditions. A vulnerability intelligence platform can help keep those CVE and asset decisions together, while the configuration match remains an owner check. Similarly, provisioned APM alone does not meet the policy condition for CVE-2026-123637.

F5 classifies each record as a stack-based buffer overflow, CWE-121. That classification explains why a traffic-processing defect can affect more than availability. It does not establish that remote code execution has occurred in a deployed environment.

What Happens on the Data Plane?

For each listed configuration, F5 says an unauthenticated remote party can send undisclosed requests that terminate TMM. The immediate, stated consequence is disrupted traffic during TMM restart. F5 also says the same flaws may permit remote code execution, so patch priority should reflect both possible outcomes.

All six F5 records assign CVSS 3.1 of 9.8 Critical and CVSS 4.0 of 9.3 Critical. These are vendor scores for the flaws, not a measure of whether a particular virtual server has the trigger. Configuration review and version review are both needed before an owner can scope exposure.

Brandefense Blackhole recorded one dark-chat post mentioning CVE-2026-116953, one mentioning CVE-2026-120285, and one mentioning CVE-2026-120292. Each count measures posts for its own CVE from August 20 through November 18, 2026. The searches may overlap, so these counts must not be added or treated as evidence of exploitation.

Which Builds Should Owners Verify?

F5’s affected-version data names engineering hotfix builds as unaffected transition points. For classic BIG-IP, it lists BIGIP-21.1.0.4.0.19.3-ENG on the 21.1 branch. The 17.5 branch lists BIGIP-17.5.1.10.0.80.35-ENG and BIGIP-17.5.1.11.0.61.12-ENG; the 17.1 branch lists BIGIP-17.1.3.6.0.14.20-ENG and BIGIP-17.1.3.7.0.21.4-ENG.

For the Next product rows that the records list, unaffected transitions are BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, and BNK-2.2.5-EHF1. Match the installed product, branch and exact hotfix identifier against its F5 advisory before marking a virtual server remediated. The record does not provide a single ordinary version threshold that safely replaces those branch-specific checks.

F5 marks earlier versions within the listed branches as affected and sets the default status of other versions to unknown. It says end-of-technical-support releases were not evaluated. An unlisted release therefore needs a vendor-supported assessment, especially where the conditional iRule or APM policy is present.

How Should Teams Sequence the Patch Decision?

First, identify internet-facing virtual servers and match their attached iRules, HTTP profiles and APM policies to the six conditions. Use the product rows to identify the correct patch family.

F5 BIG-IP patch decision
  • Inventory each BIG-IP and Next deployment, its exact build, and the virtual servers it serves.
  • Check attached iRules for the five named commands and verify that an HTTP profile is present for the PSC::ip_address and MR::message route conditions.
  • Check APM per-request policies for both Client Information and Endpoint Security agents.
  • Prioritize exposed matching configurations, obtain the applicable F5 hotfix, and schedule a traffic-aware upgrade.
  • Verify the installed build after the upgrade and watch TMM restarts and traffic availability.

F5’s six records state no workaround. Changing or removing a triggering configuration could alter service behavior, so treat that as an operational decision requiring local validation. The patch path remains the listed, applicable hotfix with a post-upgrade build check.

For asset discovery context, see how external attack surfaces are inventoried. The older BIG-IP CVE-2023-46747 analysis covers a separate flaw and should not substitute for these six configuration checks.

Frequently Asked Questions

Does every BIG-IP virtual server need the same action?

No. F5 describes different iRule, HTTP-profile and APM-policy conditions. Match each virtual server and installed build to the applicable record and advisory.

Do the six records confirm remote code execution in the wild?

The F5 records describe remote code execution as possible. They state TMM termination and traffic disruption as direct effects of the described requests.

How should a team handle the CVE-2026-121805 Next rows?

F5 lists Next products, but their module labels name DNS::scrape rather than PEM::subscriber. Confirm the Next scope with F5 before relying on those rows.

Sources

  1. F5 CVE record: CVE-2026-116953
  2. F5 CVE record: CVE-2026-120285
  3. F5 CVE record: CVE-2026-120292
  4. F5 CVE record: CVE-2026-120722
  5. F5 CVE record: CVE-2026-121805
  6. F5 CVE record: CVE-2026-123637
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →