November 20, 2026
← All advisories

F5 BIG-IP Emergency Hotfixes for Critical APM and iRules Flaws

Red Tiger Security infographic: F5 BIG-IP emergency hotfixes, 18 November 2026. A left-to-right cross-section shows remote users on the internet passing through the BIG-IP and Access Policy Manager gateway into the industrial demilitarized zone, with jump hosts and historian and SCADA web portals, then to the control network and plant floor. The gateway box lists the flaws: APM CVE-2026-123637 (per-request policy with endpoint checks) and CVE-2026-126822 (SAML, high, 7.5), and iRules CVE-2026-120292, CVE-2026-120285, CVE-2026-116953 and CVE-2026-121805 (Policy Enforcement Manager). Affected versions are 17.1.0 to 17.1.3, 17.5.0 to 17.5.1 and 21.1.0. Shadowserver sees more than 177,000 BIG-IP systems online, more than 14,600 with APM. Four steps: patch under change control, check what is configured, shrink exposure and require multifactor authentication, and watch for traffic engine restarts. F5 patched an exploited APM zero-day, CVE-2026-94127, in September 2026.

F5 released emergency out-of-band engineering hotfixes for its BIG-IP application delivery platform on Wednesday, 18 November 2026. Five of the flaws are rated critical at 9.8 on the Common Vulnerability Scoring System (CVSS) version 3.1. All five are stack-based buffer overflows in the Traffic Management Microkernel (TMM), the part of BIG-IP that handles live traffic. F5 says a remote attacker with no login can crash TMM, which disrupts traffic while it restarts, and may be able to run code remotely. F5 also says there is no control plane exposure, meaning the flaws sit in the traffic path and not the management interface, and that there is no mitigation for the five critical flaws other than installing the fix.

Each flaw only applies when a specific feature is configured on a virtual server, which is the address and port BIG-IP listens on for users:

  1. CVE-2026-123637 affects BIG-IP Access Policy Manager (APM), the remote access and virtual private network (VPN) gateway, when a per-request policy that includes the Client Information and Endpoint Security agents is applied.
  2. CVE-2026-120292, CVE-2026-120285 and CVE-2026-116953 affect any BIG-IP module when an iRule, which is a custom traffic script, uses the MR::message route, PSC::ip_address or GENERICMESSAGE::route commands. The first two also require an HTTP profile.
  3. CVE-2026-121805 affects BIG-IP Policy Enforcement Manager (PEM), plus BIG-IP CNF and BIG-IP Next for Kubernetes, when an iRule uses the PEM::subscriber command.

F5 also fixed CVE-2026-126822, a high-severity flaw rated 7.5 that lets a remote attacker with no login crash TMM when APM is set up as a Security Assertion Markup Language (SAML) service provider for single sign-on. For that one, F5 says to remove the SAML Auth agent if you do not need it and to limit access to that virtual server to trusted networks. Affected BIG-IP versions are 17.1.0 through 17.1.3, 17.5.0 through 17.5.1 and 21.1.0. The fixes are engineering hotfixes built on 17.1.3.6, 17.1.3.7, 17.5.1.10, 17.5.1.11 and 21.1.0.4, and F5 publishes a separate article (K000164239) to help pick the right build. F5 notes that engineering hotfixes do not get the full testing of a scheduled release.

F5 has not flagged any of these flaws as exploited, and none are on the Cybersecurity and Infrastructure Security Agency (CISA) Known Exploited Vulnerabilities catalog. Still, F5 gear is a favorite target. In September 2026, F5 patched another critical APM flaw, CVE-2026-94127, that attackers were already using, and it went on the CISA catalog. The Shadowserver Foundation currently sees more than 177,000 BIG-IP systems on the internet, including more than 14,600 addresses that look like APM. The Dutch National Cyber Security Centre (NCSC-NL) published advisory NCSC-2026-0508 on this release on 19 November.

Where this shows up from the plant floor to the cloud: BIG-IP is rarely inside the control system itself, but it often guards the way in. Many utilities, pipelines and manufacturers use APM as the remote access gateway that engineers, operators and vendors log into before they reach jump hosts in the industrial demilitarized zone (DMZ). BIG-IP also sits in front of historian web portals, supervisory control and data acquisition (SCADA) web screens and other plant-facing web applications. If that gateway crashes, remote support for the plant goes down with it. If someone can run code on it, they are standing at the front door of the DMZ.

What to do now

  1. Find every BIG-IP you own, including any your integrator, managed service provider or corporate information technology team runs in front of plant systems, and check the version. Install the matching engineering hotfix from F5 through your normal change control, and take a configuration backup first. Plan the change for a maintenance window, because traffic stops while TMM restarts.
  2. Check whether the vulnerable features are actually in use. Search your iRules for the PEM::subscriber, MR::message, PSC::ip_address and GENERICMESSAGE::route commands, and review APM access policies for per-request policies with the Client Information and Endpoint Security agents and for SAML service provider setups. Systems that use these features go to the front of the patch line. If you do not need SAML on APM, remove the SAML Auth agent as F5 recommends.
  3. Shrink what can reach BIG-IP. Keep the management interface off the internet and off the business network, limit plant-facing virtual servers to the networks that truly need them, and put any public remote access portal behind multifactor authentication.
  4. Watch for unexpected TMM restarts and core files in the BIG-IP logs, because that is what these flaws look like when someone triggers them. Send BIG-IP and APM logs to a central log system or your security operations center (SOC), and review remote access logins for accounts, times or locations that do not fit.

Red Tiger can help you see how remote access really reaches your control system. During our onsite facility assessments, our team walks the system from the perimeter through the DMZ and control room down to the field devices, and we often find remote access gateways and web front ends that reach deeper into the plant than anyone expected. We can then help remediate and harden what we find, and we can install a firewall and sensor at the site, connect them to the Red Tiger 24x7 SOC, and monitor the site for ongoing detection and response, with regular metrics and reports. Our team has completed more than 500 assessments and trained more than 4,500 people.

We are here to help, so check out our resources online at www.redtigersecurity.com and book a follow-up call with our team if you have any questions: https://calendly.com/jonathanpollet/30min

Source: F5 security advisories K000163937, K000163939, K000163940, K000163941, K000163942 and K000163946, 18 November 2026: https://my.f5.com/manage/s/article/K000163937

← All advisories

Cite this advisory: Red Tiger Security, "F5 BIG-IP Emergency Hotfixes for Critical APM and iRules Flaws", November 20, 2026, https://www.redtigersecurity.com/advisory/f5-big-ip-apm-irules-critical-hotfixes

Read the original source →

We are here to help.

Check out our resources and book a follow-up call with our team.

+1.877.387.7733