Affects F5 BIG-IP (widely deployed load balancers); unauthenticated remote DoS on data-plane can disrupt services organization-wide.
CVE-2026-59762
Unauthenticated HTTP/2 requests can exhaust BIG-IP TMM memory, causing data-plane DoS.
Is CVE-2026-59762 being exploited?
Not confirmed. CVE-2026-59762 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-59762?
CVE-2026-59762 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-59762?
Yes. A fix has been recorded for CVE-2026-59762. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-59762 affect?
CVE-2026-59762 affects F5 BIG-IP virtual servers with HTTP/2 profile enabled, TMM process (BIG-IP data plane). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-59762?
Disable HTTP/2 on affected virtual servers or restrict access; monitor TMM memory; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attacker can send HTTP/2 requests to exhaust TMM memory, degrading performance and causing data-plane DoS requiring TMM restart.
Immediate action required
- affected>= 21.1.0 and < 21.1.0.1
- affected>= 21.0.0 and < 21.0.0.3
- affected>= 17.5.0 and < 17.5.1.8
- affected>= 17.1.0 and < 17.1.3.4
- affected>= 2.3.0 and < 2.3.2
- affected>= 2.0.0 and < 2.2.3
- affected>= 1.1.0 and < 1.4.3
- affected>= 2.3.0 and < 2.3.2
- affected>= 2.0.0 and < 2.2.3
- affected>= 1.9.0 and < *
- affected>= 1.7.0 and < 1.7.18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.