F5’s Out-of-Band Alert Covers 22 BIG-IP and NGINX Flaws
F5 has issued an out-of-band security notification covering 22 vulnerabilities across BIG-IP, BIG-IQ and NGINX. Several can interrupt traffic processing, and some can potentially lead to remote code execution. The practical question for operators is which exposed services actually use the affected policy agents, iRule commands or protocol features.
The 18 November 2026 notification brings together ten NGINX issues and twelve BIG-IP or BIG-IQ issues. Some of the iRule vulnerabilities also affect BIG-IP Next for Kubernetes. Each has its own conditions and version matrix, so a product name or a high severity score alone is an incomplete exposure assessment.
Start with internet-facing traffic paths that match the critical APM or iRule conditions, then check NGINX protocol and proxy configurations. In parallel, examine access to the iControl management interfaces and the lifecycle of their credentials. The sources reviewed do not establish exploitation of these vulnerabilities in the wild.
Six critical BIG-IP issues depend on the traffic configuration
Six disclosures describe unauthenticated traffic that can terminate the Traffic Management Microkernel, or TMM, and potentially permit code execution. F5 rates each at 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0. Traffic disruption during a TMM restart is an immediate availability concern, even where code execution has not been demonstrated in a particular deployment.
The APM issue, CVE-2026-123637, requires APM to be provisioned and a virtual server to use a per-request policy containing both the Client Information agent and Endpoint Security agents. An installed APM licence, by itself, does not establish that the vulnerable traffic path is enabled.
The other five require a particular iRule command to process traffic on a virtual server:
- CVE-2026-120285 concerns
PSC::ip_address, with an HTTP profile also configured. - CVE-2026-120292 concerns
MR::message route, again with an HTTP profile. - CVE-2026-116953 concerns
GENERICMESSAGE::route. - CVE-2026-120722 concerns
DNS::scrape; F5 identifies BIG-IP DNS and BIG-IP Next for Kubernetes in its affected-product tables. - CVE-2026-121805 concerns
PEM::subscriber; the product tables identify BIG-IP PEM and BIG-IP Next for Kubernetes.
For all five iRule issues, the BIG-IP Next for Kubernetes tables include the 2.2, 2.3 and 2.4 branches, with fixes named BNK-2.2.5-EHF1, BNK-2.3.4-EHF1 and BNK-2.4.2-EHF1. Those builds belong to that product. They are not interchangeable with the engineering hotfixes for a conventional BIG-IP installation.
F5 lists no mitigation for these six issues. That makes checking the actual attached configuration especially important: determine which virtual servers meet the conditions and plan the applicable supported fix. Restricting a management network does not remove an exposed data-plane path.
Primary advisories: K000163937, K000163939, K000163940, K000163941, K000163945 and K000163946.
Four further APM issues can disrupt access services
The remaining APM disclosures also require specific features. Check the access profile and policy attached to each service, including older or rarely used virtual servers.
- CVE-2026-125272 affects a per-request policy containing a form-based Logon Page. Matching requests can terminate TMM without authentication.
- CVE-2026-126822 concerns a virtual server whose APM access profile acts as a SAML Service Provider. F5 describes unauthenticated denial of service.
- CVE-2026-126336 concerns a SAML Service Provider agent using encrypted assertions. It is another unauthenticated TMM denial-of-service condition, with a different fix matrix.
- CVE-2026-121812 requires an APM access profile, a per-request policy and the
tmm.access.policytracedatabase setting to be enabled. That setting is disabled by default. The notification also names BIG-IP SSL Orchestrator; the sources differ on authentication requirements and fix details, as discussed below.
F5 lists no mitigation for the form-based Logon Page issue or the policy-tracing issue. For the SAML Service Provider issue, it advises removing the SAML Auth agent if that function is unnecessary and restricting access to trusted client networks. Its high-availability advice for the encrypted-assertions issue can reduce disruption, but does not make the vulnerable code fixed.
Primary advisories: K000163938, K000163942, K000163943 and K000163944.
iControl brings a different access problem
CVE-2026-125274 affects iControl SOAP. An attacker needs network access to the interface and an authenticated account with at least the Guest role. F5 says the resulting management-request injection can allow system commands, file creation or deletion, and service disruption. This is a control-plane issue.
The SOAP advisory lists BIG-IP and BIG-IQ Centralized Management. It names BIG-IP fixes including 21.1.0.3, 17.5.1.10 and 17.1.3.6, and BIG-IQ 8.4.2.3. Removing access for users who are not fully trusted and restricting management connectivity can reduce exposure while a fix is arranged. F5 warns that changing self-IP port-lockdown settings can affect management access and high-availability services, so those changes need a deployment-specific plan.
CVE-2026-120718 concerns iControl REST token expiry. An attacker must already possess a token and may be able to prolong its lifetime unless its owner deletes it. Review automation that creates tokens: F5 recommends explicitly deleting them after their useful life. A timeout assumption is insufficient for the affected behaviour.
The REST advisory lists BIG-IP fixes at 21.1.0.2, 17.5.1.10 and 17.1.3.6. Its BIG-IQ applicability differs from the published CNA record, so BIG-IQ operators should obtain clarification rather than infer their status from the BIG-IP row.
Primary advisories: K000163936 and K000163929.
Five NGINX memory-safety flaws need protocol and proxy checks
Five NGINX disclosures describe memory corruption or use-after-free conditions with possible code execution. F5 makes that code-execution risk conditional on Address Space Layout Randomization, or ASLR, being disabled or bypassed. These conditions must remain visible when assessing the risk; a worker crash and reliable remote code execution are different outcomes.
- CVE-2026-123634 affects resolver use when a variable-based proxied server name is resolved again by an SSI or mirror subrequest. The matching request can trigger use-after-free.
- CVE-2026-123007 affects HTTP/2 flow control. An excessive flow-control window can produce a heap buffer overflow and a worker crash.
- CVE-2026-123633 affects HTTP/2 connections that proxy requests to a backend when the worker is running short of available connections. The relevant setting is
worker_connections. - CVE-2026-121810 affects HTTP/3 and can cause use-after-free and a worker restart. F5 also states that exploitation depends on circumstances outside the attacker’s control.
- CVE-2026-113425 affects NGINX acting as a mail proxy. A crafted mail session can cause use-after-free, corrupt memory or terminate the worker.
Each is rated 8.1 under CVSS v3.1 and 9.2 under CVSS v4.0. The version tables identify NGINX Open Source 1.31.9 and 1.30.7 as fixed releases for these five issues. NGINX Plus fixes vary by branch and issue; several tables name 37.3.0.1 and 37.0.8.1, while some issues have earlier Plus fixes. Check the individual table against the installed build.
For the resolver issue, F5 advises avoiding the relevant SSI or mirror use and variable-based upstream names. For the mail-proxy issue, it advises restricting listeners to trusted networks. No mitigation is listed for the three HTTP/2 and HTTP/3 issues. Changes to protocol or proxy behaviour can affect applications and need testing.
Primary advisories: K000163925, K000163926, K000163928, K000163927 and K000163931.
The other NGINX issues include trust and routing failures
Availability is only part of the NGINX assessment. Two issues can undermine assumptions about certificate checks or which backend a connection can reach.
- CVE-2026-120967 can bypass client-certificate verification when it is required in a non-default stream virtual server. F5’s mitigations include requiring verification in the default server on the shared socket, or giving the protected virtual server its own listening address and port.
- CVE-2026-123640 concerns forged SSL preread variables. A crafted ClientHello can influence routing and potentially reach an internal or privileged backend. F5 describes replacing preread-based handling with TLS termination on NGINX as a mitigation; this is an architectural change requiring certificate, routing and backend checks.
- CVE-2026-120993 can terminate a worker when stream SSL uses dynamic certificate loading alongside PROXY protocol v2 and an abbreviated handshake. F5 lists protocol or session-resumption changes as mitigations and says builds using BoringSSL or AWS-LC are unaffected.
- CVE-2026-125283 can crash a worker through particular combinations of
try_files,alias, a map variable and regular-expression captures. F5 recommends named captures and avoiding reuse of capture variables. - CVE-2026-118899 can leave an NGINX worker in an endless loop while reading an HTTP request body over a crafted TLS connection. It requires an HTTP SSL listener with TLS 1.3 enabled. The affected worker stops processing existing connections and accepting new ones.
Primary advisories: K000163934, K000163935, K000163932, K000163933 and K000163930.
Select the engineering hotfix for the build actually installed
F5 has published separate engineering-hotfix selection guidance for the November notification. On BIG-IP 17.1 and 17.5, the correct target depends on whether the device is running a named earlier engineering hotfix or a base release.
For example, an installation on BIGIP-17.1.3.6.0.9.20-ENG is directed to BIGIP-17.1.3.6.0.14.20-ENG. A 17.1.3.7 base release, or an earlier base release, is directed to BIGIP-17.1.3.7.0.21.4-ENG. The guidance separately maps two existing 17.5.1.10 engineering hotfixes to BIGIP-17.5.1.10.0.80.35-ENG, and the 17.5.1.11 base-release path to BIGIP-17.5.1.11.0.61.12-ENG. Its 21.1.0.4 base-release path uses BIGIP-21.1.0.4.0.19.3-ENG.
Use the full selection document before downloading a build, particularly where a device already has an engineering hotfix. F5 directs customers on a custom engineering hotfix to Support for an appropriate new build. An older fix for one issue in this notification does not establish coverage for the other 21.
Publication-day source differences need confirmation
The live F5 articles and F5’s published CNA records are not fully aligned on every detail. These differences affect decisions and should remain explicit:
- For CVE-2026-120718, the live REST advisory labels BIG-IQ as not vulnerable, while the F5 CNA record includes an affected BIG-IQ range. Confirm BIG-IQ applicability with F5.
- For CVE-2026-121812, the live policy-tracing advisory describes an authenticated attacker, while the CNA description says unauthenticated. The fix details also differ. Neither the authentication boundary nor an older base-release fix should be assumed settled.
- For CVE-2026-118899, the live TLS 1.3 table lists Open Source 1.13.0 with no fix, while the CNA version data contains 1.30 and 1.31 ranges, including an overlapping open-ended range. Do not infer a universal Open Source fix from those conflicting entries. The HTTP/3 CNA also contains an unusual version string, so use the live advisory and vendor confirmation for exact applicability.
These are source discrepancies, not evidence that an affected deployment is safe. Record the uncertainty in the change plan and check for revised vendor guidance before making a version-specific closure claim.
Turn the notification into a verified change
- Inventory the running systems. Record the product, full build, engineering-hotfix status, enabled modules and attached traffic policies. Include Next for Kubernetes, NGINX containers and embedded reverse proxies in the assessment.
- Map the exposed features. Identify the relevant iRule commands, APM agents, HTTP versions, mail proxy, stream TLS, preread routing and management access. This produces an actionable exposure list for service owners.
- Choose a supported update path. Match each relevant advisory to the current branch and F5’s hotfix-selection instructions. The vendor does not evaluate releases already beyond End of Technical Support. Check support dates alongside the vulnerability assessment, using the BlackTree Lifecycle catalogue where an applicable record is available.
- Protect service recovery. Preserve configuration backups, confirm failover and rollback arrangements, and test representative application, authentication and routing behaviour. Treat configuration mitigations as changes with their own operational effects.
- Verify the deployed outcome. Confirm the new build is actually running, required policies still work and workers remain healthy. Test expected client-certificate rejection, permitted backend routing and legitimate access flows. Retain the installed build and advisory evidence with the change record.
The useful completion measure is a service whose running build and configuration have been checked against its relevant advisories. A downloaded hotfix, an untouched standby device or a closed change ticket alone does not provide that evidence.


