CVE-2026-59762: F5 BIG-IP HTTP/2 Memory Exhaustion Denial of Service
- Vendor
- F5
CVE-2026-59762 is a resource-exhaustion vulnerability affecting F5 BIG-IP and related BIG-IP Next products when an HTTP/2 profile is configured on a virtual server. Crafted requests can increase memory utilization in the Traffic Management Microkernel (TMM), degrading performance until TMM is manually restarted or forced to restart. The vulnerability is associated with inadequate limits on buffered response data when HTTP/2 clients stall outbound flow control. Exploitation is remote and unauthenticated and affects the data plane only, with no control plane exposure.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can exhaust memory, degrade traffic-processing performance, and cause denial of service for legitimate clients. Resource pressure can force a TMM restart, or an administrator may need to restart TMM to restore service. The identified impact is availability loss on the data plane; confidentiality and integrity impacts are not identified.
Mitigation
If you can’t patch tonight, do this now.
Where supported, enforce memory ceilings for buffered HTTP/2 responses, restrict concurrent streams per connection, and terminate connections exhibiting stalled flow control. Appropriate timeout and backpressure handling can reduce resource accumulation. Validate these measures against F5 product-specific guidance; they are general mitigations for the underlying HTTP/2 issue, not confirmed substitutes for the F5 fixes. Restarting TMM may restore service after degradation but does not remove the vulnerability or prevent recurrence.
Remediation
Patch, then assume compromise.
Apply F5 fixes for the applicable product and release branch. Listed fixed BIG-IP releases are 21.1.0.1, 21.0.0.3, 17.5.1.8, and 17.1.3.4. Listed fixed BIG-IP Next for Kubernetes releases are 2.3.2 and 2.2.3; BIG-IP Next CNF releases are 2.3.2, 2.2.3, and 1.4.3; and BIG-IP Next SPK 1.7 is fixed in 1.7.18. A fixed release for the affected SPK 1.9-and-later branch is not specified. Consult F5 advisory K000162231 for current branch-specific upgrade guidance. End-of-Technical-Support versions were not evaluated and should not be assumed unaffected.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-59762 exploited in the wild?
- As of Oct 15, 2026, Mallory has no reports of CVE-2026-59762 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-59762?
- As of Oct 15, 2026, Mallory has found no public exploit for CVE-2026-59762.
- Is there a patch for CVE-2026-59762?
- Apply F5 fixes for the applicable product and release branch. Listed fixed BIG-IP releases are 21.1.0.1, 21.0.0.3, 17.5.1.8, and 17.1.3.4.
- What products are affected by CVE-2026-59762?
- F5 Big-Ip Next Cloud-Native Network Functions, F5 Big-Ip Next For Kubernetes, and F5 Big-Ip Next Service Proxy For Kubernetes.
- How severe is CVE-2026-59762?
- CVE-2026-59762 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.57% (48th percentile) as of Oct 15, 2026.
Recent activity
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.