BIG-IP
CVE-2026-59762: BIG-IP HTTP/2 vulnerability
When an HTTP/2 profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization.
Published
Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.
Affected and fixed versions
| Product / branch | Fixed in |
|---|---|
| BIG-IP 21.1 | 21.1.0.1 or later |
| BIG-IP 21.0 | 21.0.0.3 or later |
| BIG-IP 17.5 | 17.5.1.8 or later |
| BIG-IP 17.1 | 17.1.3.4 or later |
| BIG-IP Next for Kubernetes 2.3 | 2.3.2 or later |
| BIG-IP Next for Kubernetes 2.0 | 2.2.3 or later |
| BIG-IP Next SPK 1.9 | * or later |
| BIG-IP Next SPK 1.7 | 1.7.18 or later |
| BIG-IP Next CNF 2.3 | 2.3.2 or later |
| BIG-IP Next CNF 2.0 | 2.2.3 or later |
| BIG-IP Next CNF 1.1 | 1.4.3 or later |
Always confirm against the vendor advisory, which lists every fixed hotfix.
What it is
When an HTTP/2 profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization.
Impact: System performance can degrade until the TMM process is either forced to restart or is manually restarted. This vulnerability allows a remote, unauthenticated attacker to cause a degradation of service that can lead to a denial-of-service (DoS) on the BIG-IP system. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Sources
KEV status, EPSS score and vendor data refreshed automatically, last on 12 Oct 2026.