F5 BIG-IP and BIG-IQ Vulnerabilities: November 18, 2026

F5’s out-of-band notification lists 12 BIG-IP and BIG-IQ advisories. Most need a specific module or configuration to apply, and nine are fixed only in engineering hotfixes so far.

See all 12 CVEs
By CalMax Systems Security Research · Published November 18, 2026 · Last updated: November 18, 2026

What should I do about F5’s November 18, 2026 BIG-IP fixes?

Check your BIG-IP version and configuration against the table below, then install the build F5 names. Three of the flaws are fixed in point releases (BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6; BIG-IQ 8.4.2.3). The other nine are fixed only in engineering hotfixes, and F5’s K000164239 says which hotfix build to install for the version you run now.

F5 published 12 BIG-IP and BIG-IQ advisories in an out-of-band notification. Ten let a remote attacker crash TMM on the data plane, and for six of those F5 says code execution may also be possible. Neither F5 nor CISA reports any exploitation as of November 18, 2026. Most of the flaws need a specific module or configuration, but the iControl SOAP flaw affects every BIG-IP on an affected release, so keep the management interface and self IP addresses closed to untrusted networks.

All 12 BIG-IP and BIG-IQ CVEs

Sorted by severity. Every BIG-IP row affects 21.1.0, 17.5.0 through 17.5.1, and 17.1.0 through 17.1.3 unless noted. The configuration column is what F5 says must be present for the flaw to apply.

CVE and F5 article Component and required configuration Impact CVSS v3.1 / v4.0 Fixed in
CVE-2026-123637
K000163937
BIG-IP APM: a per-request policy that includes the Client Information agent and Endpoint Security agents, applied to a virtual serverTMM crash (DoS); RCE possible. Unauthenticated. Data plane onlyCritical 9.8 / Critical 9.3Engineering hotfix only
CVE-2026-120285
K000163939
BIG-IP, all modules: an HTTP profile and an iRule containing PSC::ip_address on a virtual serverTMM crash (DoS); RCE possible. Unauthenticated. Data plane onlyCritical 9.8 / Critical 9.3Engineering hotfix only
CVE-2026-120292
K000163940
BIG-IP, all modules: an HTTP profile and an iRule using MR::message route on a virtual serverTMM crash (DoS); RCE possible. Unauthenticated. Data plane onlyCritical 9.8 / Critical 9.3Engineering hotfix only
CVE-2026-116953
K000163941
BIG-IP, all modules: an iRule that processes client traffic with GENERICMESSAGE::route on a virtual serverTMM crash (DoS); RCE possible. Unauthenticated. Data plane onlyCritical 9.8 / Critical 9.3Engineering hotfix only
CVE-2026-120722
K000163945
BIG-IP DNS: an iRule that processes client traffic with DNS::scrape on a virtual serverTMM crash (DoS); RCE possible. Unauthenticated. Data plane onlyCritical 9.8 / Critical 9.3Engineering hotfix only
CVE-2026-121805
K000163946
BIG-IP PEM: an iRule that processes client traffic with PEM::subscriber on a virtual serverTMM crash (DoS); RCE possible. Unauthenticated. Data plane onlyCritical 9.8 / Critical 9.3Engineering hotfix only
CVE-2026-125274
K000163936
BIG-IP, all modules, and BIG-IQ Centralized Management 8.4.0 through 8.4.2: iControl SOAP, reached by a user with at least the Guest roleRun arbitrary system commands, create or delete files, or disable services. Authenticated (Guest or higher). Control plane onlyHigh 8.8 / High 8.7BIG-IP 21.1.0.3, 17.5.1.10, 17.1.3.6; BIG-IQ 8.4.2.3
CVE-2026-120718
K000163929
BIG-IP, all modules: iControl REST tokens may not expire as expectedAn attacker who has already obtained a token may be able to extend its lifetime unless the owner deletes it. Control plane only (per F5’s CVE record)High 8.1 / Critical 9.2BIG-IP 21.1.0.2, 17.5.1.10, 17.1.3.6
CVE-2026-125272
K000163938
BIG-IP APM: a virtual server with an APM access profile and a per-request policy containing a form-based Logon PageTMM crash (DoS). Unauthenticated. Data plane onlyHigh 7.5 / High 8.7Engineering hotfix only
CVE-2026-126822
K000163942
BIG-IP APM: a virtual server with an access profile configured as a SAML Service Provider (SP)TMM crash (DoS). Unauthenticated. Data plane onlyHigh 7.5 / High 8.7Engineering hotfix only
CVE-2026-126336
K000163943
BIG-IP APM: a virtual server with an APM access profile and a SAML SP agent with encrypted assertions enabledTMM crash (DoS). Unauthenticated. Data plane onlyHigh 7.5 / High 8.7BIG-IP 21.1.0.3, 17.5.1.10, 17.1.3.6
CVE-2026-121812
K000163944
BIG-IP APM and BIG-IP SSL Orchestrator: a virtual server with an APM access profile and a per-request policy, with the tmm.access.policytrace database key enabled (off by default). SSL Orchestrator rows list 21.1.0, 17.5.0 and 17.1.0 through 17.1.3TMM crash (DoS). F5’s advisory says authenticated; its CVSS vector and CVE record say no privileges required. Data plane onlyHigh 7.5 / High 8.7Engineering hotfix only (see the SSL Orchestrator note below)
How to read the table. “Engineering hotfix only” means F5’s advisory lists no point release yet, only these builds: BIGIP-21.1.0.4.0.19.3-ENG for 21.1; BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG for 17.5; BIGIP-17.1.3.7.0.21.4-ENG or BIGIP-17.1.3.6.0.14.20-ENG for 17.1. Which one you install depends on what you run now (see How to update). F5 notes that once a release in a branch fixes a flaw, every later release in that branch has the fix too. That does not make a later base release safe from the hotfix-only flaws: F5’s K000164239 still sends the 21.1.0.4, 17.5.1.11 and 17.1.3.7 base releases to an engineering hotfix. F5 evaluates only releases that have not reached End of Technical Support, so an older branch missing from the table has not been assessed; that does not mean it is safe.
Where F5’s sources differ: ask F5 Support. For CVE-2026-121812, the SSL Orchestrator row lists 17.5.0 as affected but names only the two 17.1 hotfixes, so ask F5 which build covers SSL Orchestrator on 17.5. F5’s CVE record for CVE-2026-121812 also lists 21.1.0.3, 17.5.1.10 and 17.1.3.6 as the upper bounds of the affected range, while the advisory lists only engineering hotfixes; this page follows the advisory. For CVE-2026-120718, the advisory marks BIG-IQ as not vulnerable, while F5’s CVE record lists BIG-IQ from 8.4.0 up to, but not including, 8.4.2.3 as affected.

Which Ones Apply to You

Most of these flaws need a module to be provisioned and a feature to be in use on a virtual server. Check each item against your configuration.

Any BIG-IP, whatever the module

BIG-IP APM

BIG-IP DNS, PEM and SSL Orchestrator

BIG-IQ and other F5 products

F5’s advisories list BIG-IQ Centralized Management 8.4.0 through 8.4.2 as affected only by the iControl SOAP flaw, CVE-2026-125274, fixed in 8.4.2.3 (see the CVE-2026-120718 note above). F5’s advisories also list BIG-IP CNF and BIG-IP Next for Kubernetes 2.2.0 through 2.4.2 as affected by the iRule flaws, with CNF and BNK engineering hotfixes in the F5 Artifact Repository; check the individual advisory for your platform. The advisories list F5OS, F5 Distributed Cloud, NGINX One Console, F5 AI Gateway and F5 Insight as not vulnerable to these 12.

Find the running version

F5’s K8759: in the Configuration utility, go to System > Configuration; the version is in the Version box. From the command line, enter tmsh, then:

show /sys version

Check both units of an HA pair.

How to Update

Three of the flaws are fixed in point releases that already exist. The other nine need an engineering hotfix, and F5’s K000164239 says which build to install.

Point releases

BIG-IP 21.1.0.3, 17.5.1.10 and 17.1.3.6 fix CVE-2026-125274 (iControl SOAP) and CVE-2026-126336 (APM SAML encrypted assertions). CVE-2026-120718 (iControl REST) is fixed from 21.1.0.2, 17.5.1.10 and 17.1.3.6. BIG-IQ 8.4.2.3 fixes CVE-2026-125274. Later releases in the same branch include these fixes. A point release alone does not fix the other nine.

Engineering hotfixes: pick the build from K000164239

F5’s K000164239 covers BIG-IP 21.1.x, 17.5.x and 17.1.x and chooses the build from the version or engineering hotfix you run now. The builds are on MyF5 Downloads.

You run nowInstall this build
21.1.0.4 base release or an earlier base releaseBIGIP-21.1.0.4.0.19.3-ENG
17.5.1.11 base release or an earlier base releaseBIGIP-17.5.1.11.0.61.12-ENG
Engineering hotfix BIGIP-17.5.1.10.0.7.35-ENG or BIG-IP-17.5.1.10.0.37.35-ENGBIGIP-17.5.1.10.0.80.35-ENG
17.1.3.7 base release or an earlier base releaseBIGIP-17.1.3.7.0.21.4-ENG
Engineering hotfix BIGIP-17.1.3.6.0.9.20-ENGBIGIP-17.1.3.6.0.14.20-ENG
A custom engineering hotfix buildContact F5 Support to request a new engineering hotfix
F5’s warning about engineering hotfixes. In each of the nine hotfix-only advisories F5 says: “While F5 endeavors to release the most stable code possible, engineering hotfixes do not undergo the extensive QA assessment of scheduled software releases. F5 offers engineering hotfixes with no warranty or guarantee of usability.” F5’s hotfix policy is in K4918, and K13123 covers managing BIG-IP hotfixes. Plan a maintenance window, keep a rollback volume, and test on a standby unit first where you can.

Mitigations Until You Can Update

These are the mitigations each F5 advisory gives, quoted or closely summarized. For eight of the 12, F5 lists none.

No mitigation listed (8 advisories)

F5 lists the mitigation as “None” for CVE-2026-123637, CVE-2026-125272, CVE-2026-120285, CVE-2026-120292, CVE-2026-116953, CVE-2026-121812, CVE-2026-120722 and CVE-2026-121805. Removing the triggering configuration (the iRule command, the per-request policy agent, or the database key) changes whether the flaw applies, but F5 does not present that as a mitigation, so test any change before relying on it.

CVE-2026-125274, iControl SOAP

F5: “As this attack is conducted by legitimate, authenticated users, there is no viable mitigation that also allows users access to iControl SOAP. The only mitigation is to remove access for users who are not completely trusted.”

Until you can install a fixed version, F5 gives two temporary mitigations that limit iControl SOAP and iControl REST to trusted networks or devices:

CVE-2026-120718, iControl REST tokens

F5: “Modify scripts that create REST tokens to delete them at the end of their useful life.” F5’s CVE record adds K02126317 for listing and deleting REST tokens.

CVE-2026-126822, APM SAML Service Provider

F5: “if SAML SP is not required, remove the SAML Auth agent from the APM access policy. In addition, restrict network access to the virtual server hosting the SAML SP to trusted client networks.”

CVE-2026-126336, APM SAML encrypted assertions

F5 recommends configuring BIG-IP systems with high availability to lessen the impact: set up HA clustering (K02234544) and configure the HA table to take specific actions (K9231). This reduces the outage, not the flaw.

Exploitation Status and What to Watch

No known exploitation as of November 18, 2026, and no indicators of compromise in the advisories.

None of the 12 advisories reports exploitation. None of the 12 CVEs is in CISA’s Known Exploited Vulnerabilities catalog (catalog version 2026.11.18), and CISA’s enrichment of each CVE record marks exploitation as “none”. CISA’s enrichment marks the ten TMM crash flaws as automatable.

F5 lists no indicators of compromise in these advisories. For the ten crash flaws, F5 describes the visible effect: traffic is disrupted while the TMM process restarts. An unexplained TMM restart on a system that matches one of the configurations above is worth raising with F5 Support.

F5 credits watchTowr for eight of the 12 reports, Pentest-Tools for the iControl SOAP flaw and v3rtical for the iControl REST flaw; F5 found the DNS and PEM iRule flaws internally.

Timeline

DateEvent
September 22, 2026F5 publishes K000162605 for CVE-2026-94127, the exploited BIG-IP APM OAuth flaw. It is a separate issue, covered in our CVE-2026-94127 alert.
November 18, 2026F5 publishes the Out-of-band Security Notification K000164058 with 12 BIG-IP and BIG-IQ advisories and 10 NGINX advisories, plus K000164239 for engineering hotfix selection. The 12 CVE records are published the same day.
November 18, 2026CISA KEV catalog version 2026.11.18 does not include any of the 12 CVEs.

NGINX. The same notification lists 10 NGINX advisories, for NGINX Plus, NGINX Open Source and, for some of them, other NGINX products. This page does not cover them; see F5’s index, K000164058.

Where ThreatListPro Fits

A known-attacker list can cut down who reaches your edge. It does not fix these flaws.

These are flaws in the BIG-IP itself: most are on the data plane, in virtual servers that handle client traffic, and two are in the management APIs. Only F5’s fixed release or engineering hotfix removes them. A block list does not stop an exploit: an attacker using an address that is not on the list can still send the malicious requests.

What a block list can do is reduce the scanning and login attempts that reach internet-facing portals, such as an APM logon page. ThreatListPro covers 5.4M+ IPv4 addresses, including addresses covered by CIDR ranges. The list is built from real attacks on live production Palo Alto GlobalProtect VPN portals in the US and is checked for new attackers every 6 hours. ThreatListPro has no BIG-IP setup guide; it is loaded on the firewall in front of the BIG-IP, as a deny rule for inbound traffic. The setup instructions cover the supported firewalls. The list is IPv4 only. iControl SOAP and REST should not be reachable from the internet at all, per F5’s advice above.

F5 BIG-IP November 2026 FAQs

Are the November 2026 F5 BIG-IP vulnerabilities being exploited?

Neither F5 nor CISA reports any exploitation as of November 18, 2026. None of the 12 BIG-IP and BIG-IQ advisories reports exploitation, none of the 12 CVEs is in CISA's Known Exploited Vulnerabilities catalog, and CISA's enrichment of each CVE record marks exploitation as none. Check again before you decide to wait, because that can change.

Which of these F5 flaws may allow remote code execution?

F5 says six of them may allow an unauthenticated attacker to perform remote code execution as well as crash TMM: CVE-2026-123637 (BIG-IP APM), CVE-2026-120285, CVE-2026-120292 and CVE-2026-116953 (iRules on any BIG-IP module), CVE-2026-120722 (BIG-IP DNS) and CVE-2026-121805 (BIG-IP PEM). Each one needs a specific configuration on a virtual server. All six are rated CVSS v3.1 9.8 and CVSS v4.0 9.3.

Is there a fixed BIG-IP point release, or only engineering hotfixes?

Both, depending on the flaw. Three were already fixed in point releases: the iControl REST flaw in 21.1.0.2, 17.5.1.10 and 17.1.3.6, and the iControl SOAP and APM SAML encrypted-assertion flaws in 21.1.0.3, 17.5.1.10 and 17.1.3.6. The other nine are fixed only in engineering hotfixes for now. BIG-IQ fixes the iControl SOAP flaw in 8.4.2.3.

Which F5 engineering hotfix build should I install?

F5's K000164239 picks the build from what you run now. On 21.1.0.4 or an earlier base release, install BIGIP-21.1.0.4.0.19.3-ENG. On 17.5.1.11 or an earlier base release, install BIGIP-17.5.1.11.0.61.12-ENG; if you run the hotfix BIGIP-17.5.1.10.0.7.35-ENG or BIG-IP-17.5.1.10.0.37.35-ENG, install BIGIP-17.5.1.10.0.80.35-ENG. On 17.1.3.7 or an earlier base release, install BIGIP-17.1.3.7.0.21.4-ENG; if you run BIGIP-17.1.3.6.0.9.20-ENG, install BIGIP-17.1.3.6.0.14.20-ENG. If you run a custom engineering hotfix, contact F5 Support.

Is there a workaround if I cannot install the hotfix yet?

For most of them, no. F5 lists the mitigation as None for eight of the 12. For iControl SOAP, F5 says to remove access for users who are not completely trusted and to restrict iControl SOAP to trusted networks or devices. For the APM SAML SP flaw, remove the SAML Auth agent if SAML SP is not required and restrict the virtual server to trusted client networks. For SAML encrypted assertions, F5 recommends high availability. For iControl REST, delete tokens at the end of their useful life.

Is CVE-2026-94127 part of the November 18 release?

No. CVE-2026-94127 is a separate BIG-IP APM OAuth Authorization Server flaw that F5 published on September 22, 2026. Unlike the November 18 flaws, F5 says it has been exploited, and it is in CISA's KEV catalog. It has its own fixed versions and an iRule mitigation from F5 Support.

Sources

Block Known Attackers at the Firewall in Front

ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial and no card needed.

Start a 14-day free trial Or test the free sample first: no signup

Firewall Guides

ThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

More dated alerts, and how to block addresses at the firewall in front of an exposed service.

All Security Alerts F5 BIG-IP APM CVE-2026-94127 (exploited) Ivanti Connect Secure CVE-2026-104935 Setup Instructions for Every Supported Firewall Block an IP Address at the Firewall IP Blocklist vs Threat Feed