Takeaway: On November 18, 2026, F5 published out-of-band security notification K000164058 for BIG-IP. The NHS England alert dated November 19 says the notification addresses six critical vulnerabilities that can cause a denial-of-service condition or, in five of those cases, potentially remote code execution. The Canadian Centre for Cyber Security advisory AV26-1178, also dated November 19, lists the affected BIG-IP branches and the engineering builds to install. Confirm the exact hotfix for your release in the F5 article, which may require a MyF5 login.
The details below come from those government advisories and from France’s CERT-FR avis CERTFR-2026-AVI-1567, which cites the same F5 bulletin of November 18 as its source. Descriptions use that official wording and do not include reproduction steps. None of these advisories says the issues are being exploited in the wild, and this article does not add that claim.
What the notification covers
NHS England describes K000164058 as an out-of-band security notification for critical vulnerabilities in BIG-IP. It lists five stack-based buffer overflow issues, each with a CVSSv4 score of 9.3:
- CVE-2026-121805
- CVE-2026-120292
- CVE-2026-120285
- CVE-2026-116953
- CVE-2026-123637
The official wording is that successful exploitation could allow a remote unauthenticated attacker to cause a denial-of-service condition or potentially achieve remote code execution on affected systems. NHS separately lists CVE-2026-126822 as an integer underflow (wrap or wraparound) vulnerability with a CVSSv4 score of 8.7 that could allow a remote unauthenticated attacker to cause a denial-of-service condition.
The same NHS alert summarizes several data-plane conditions. Those include cases where BIG-IP Access Policy Manager (APM) is provisioned with certain per-request or SAML service-provider profiles, and cases where a virtual server is configured with particular iRule commands. In the described cases, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate, which disrupts traffic while TMM restarts. NHS states that there is no control plane exposure and that these are data-plane issues only. This article does not map those conditions to individual CVE identifiers. Use F5 article K000164058 for that mapping and for any configuration notes that apply to your deployment.
Software versions that have reached End of Technical Support (EoTS) are not evaluated, according to the NHS write-up, which points to F5 knowledge article K4602 for the company’s vulnerability response policy. F5 evaluates only software that has not yet reached that phase.
Affected products and fixed builds
The Cyber Centre’s AV26-1178 advisory lists these product lines and version thresholds as of November 19, 2026. The “prior to” builds below are the fixed engineering or hotfix releases named in that advisory. Confirm the package that matches your exact release on MyF5 before you install it.
| Product | Affected versions, and the fixed build listed by CCCS |
|---|---|
| BIG-IP | 17.1.0 prior to BIGIP-17.1.3.7.0.21.4-ENG; 17.5.0 prior to BIGIP-17.5.1.11.0.61.12-ENG; 21.1.0 prior to BIGIP-21.1.0.4.0.19.3-ENG |
| BIG-IP (APM) | The same 17.1, 17.5, and 21.1 thresholds and ENG builds as BIG-IP |
| BIG-IP SSL Orchestrator | The same 17.1, 17.5, and 21.1 thresholds and ENG builds as BIG-IP |
| BIG-IP PEM | The same 17.1, 17.5, and 21.1 thresholds and ENG builds as BIG-IP |
| BIG-IP CNF | 2.2.0 prior to CNF-2.2.5-EHF1; 2.3.0 prior to CNF-2.3.4-EHF1; 2.4.0 prior to CNF-2.4.2-EHF1 |
| BIG-IP Next for Kubernetes | 2.2.0 prior to BNK-2.2.5-EHF1; 2.3.0 prior to BNK-2.3.4-EHF1; 2.4.0 prior to BNK-2.4.2-EHF1 |
| BIG-IQ Centralized Management | Prior to 8.4.2.3 |
NHS England also lists F5 Insight among the platforms known to be affected, alongside BIG-IQ Centralized Management, BIG-IP (all modules), BIG-IP Cloud-Native Edition, BIG-IP CNF, and BIG-IP Next for Kubernetes. The Cyber Centre advisory quoted above does not include a separate Insight row. If you run Insight, check K000164058 rather than assuming it is or is not covered by the CCCS table.
CERT-FR, citing the same November 18 F5 bulletin, lists the same CNF, Kubernetes, 21.1, and BIG-IQ fixed builds as the Cyber Centre. For the 17.x and 17.5.x lines it also names earlier engineering builds — 17.1.3.6.0.14.20-ENG and 17.5.1.10.0.80.35-ENG — in addition to the later 17.1.3.7.0.21.4-ENG and 17.5.1.11.0.61.12-ENG builds. This article does not collapse those rows or guess which CVE each intermediate build addresses. Use the F5 notification as the source of truth for the hotfix that matches your version.
What this notification is not
CERT-FR’s avis also lists NGINX Open Source and NGINX Plus branches among the systems it associates with the same F5 bulletin, including NGINX Open Source versions prior to 1.31.9 and 1.30.7. Those NGINX releases were already covered here in the nginx 1.31.9 and 1.30.7 security update. This article is about the BIG-IP out-of-band notification and the BIG-IP, CNF, Kubernetes, and BIG-IQ builds listed above. It does not treat the nginx updates as a substitute for the BIG-IP hotfixes, or the other way around.
The government advisories cited here do not publish a workaround in place of the vendor fixes. NHS encourages affected organizations to review K000164058 and apply the relevant updates as soon as possible. The Cyber Centre likewise encourages administrators to review the provided links and apply any necessary updates. This article does not invent a configuration workaround.
These BIG-IP fixes sit alongside, rather than instead of, other stack updates. A VMware VMSA-2026-0009 update or the November 2026 PHP security releases still need to be applied on their own schedules if they apply to your environment.
Key facts
| Item | What official sources say |
|---|---|
| Vendor notification | F5 K000164058, dated November 18, 2026, cited by CERT-FR, NHS England, and the Canadian Centre for Cyber Security. |
| Government alerts | CERTFR-2026-AVI-1567 (November 18, 2026); NHS CC-4898 and CCCS AV26-1178 (November 19, 2026). |
| Critical BIG-IP CVEs listed by NHS | CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, and CVE-2026-123637, each a stack-based buffer overflow with a CVSSv4 score of 9.3. |
| Additional CVE listed by NHS | CVE-2026-126822, an integer underflow with a CVSSv4 score of 8.7, described as a denial-of-service issue. |
| Exposure | NHS describes the summarized conditions as data-plane issues only, with no control plane exposure. |
| In-the-wild status | The cited advisories do not state that these issues are being exploited, and this article does not add that claim. |
| Workarounds | The cited government advisories point to the F5 updates; they do not list a substitute workaround, and this article does not invent one. |
| Source of truth for patches | F5 article K000164058, with the CCCS version table used here as a government-published summary of those builds. |
FAQ
What did F5 publish on November 18, 2026?
An out-of-band security notification, K000164058, covering critical vulnerabilities in BIG-IP. NHS England, the Canadian Centre for Cyber Security, and CERT-FR all point to that F5 article.
Which CVEs does NHS list?
Five stack-based buffer overflow issues — CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, and CVE-2026-123637 — each with a CVSSv4 score of 9.3, plus CVE-2026-126822, an integer underflow with a CVSSv4 score of 8.7.
Do these issues allow remote code execution?
NHS says the five buffer overflow issues could allow a remote unauthenticated attacker to cause a denial-of-service condition or potentially achieve remote code execution. It describes CVE-2026-126822 as a denial-of-service issue. This article does not add exploit detail.
Which BIG-IP versions should I install?
The Cyber Centre lists BIGIP-17.1.3.7.0.21.4-ENG, BIGIP-17.5.1.11.0.61.12-ENG, and BIGIP-21.1.0.4.0.19.3-ENG for the corresponding 17.1, 17.5, and 21.1 branches, plus named EHF1 builds for CNF and BIG-IP Next for Kubernetes, and BIG-IQ 8.4.2.3. Confirm the exact package for your release in F5 article K000164058.
Are older BIG-IP versions that have reached end of support included?
NHS notes that F5 evaluates only software versions that have not yet reached the End of Technical Support phase. EoTS versions are not evaluated in the notification, and this article does not invent patches for them.
Is this the same as the November 2026 nginx security updates?
No. CERT-FR lists some NGINX branches in a bulletin that cites the same F5 article, but the nginx 1.31.9 and 1.30.7 updates are a separate patch set, already covered on this site. Apply the BIG-IP hotfixes and any nginx updates that apply to your stack on their own schedules.
Is there an official workaround if I cannot patch immediately?
The government advisories cited here point to the F5 updates and do not publish a substitute workaround. This article does not invent one. Review K000164058 for any vendor guidance that applies to your configuration.
Have these vulnerabilities been exploited in the wild?
The F5, NHS, Cyber Centre, and CERT-FR notices cited in this article do not state that the issues are being exploited in the wild. This article does not add that claim.
