Big Ip Next Cloud Native Network FunctionsApplication · F5
CVE-2026-59762
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen 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.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a memory exhaustion vulnerability in the F5 BIG-IP data plane (TMM) where undisclosed HTTP/2 requests cause unbounded memory growth when an HTTP/2 profile is configured on a virtual server. The memory leak eventually forces TMM restart or manual intervention, allowing remote unauthenticated attackers to cause denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Big Ip Next Cloud Native Network FunctionsApplication
>= 1.1.0, < 1.4.3>= 2.0.0, < 2.2.3= 2.3.0
Big Ip Next For KubernetesApplication
>= 2.0.0, < 2.2.3= 2.3.0
Big Ip Next Service Proxy For KubernetesApplication
>= 1.7.0, < 1.7.18>= 1.8.0, <= 1.9.2>= 2.0.0, <= 2.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify BIG-IP system and versionRun `tmsh show /sys version` or check the web UI (System > Software Management > ISO Image) to determine the BIG-IP version. Compare against any affected version range if published.Affected if The system is F5 BIG-IP and the installed version falls within an affected range (if known).
-
Verify HTTP/2 profile existenceRun `tmsh list /ltm http2` to list all HTTP/2 profiles configured on the system. If no profiles are returned, the vulnerability does not apply.Affected if Any HTTP/2 profile exists on the system.
-
Check virtual servers with HTTP/2 enabledRun `tmsh list /ltm virtual` and inspect each virtual server for an http2 profile reference in the configuration. Alternatively, use `tmsh list /ltm virtual <name> | grep -i http2` for each virtual server.Affected if Any virtual server has an HTTP/2 profile assigned to it.
-
Assess network exposureConfirm that affected virtual servers are reachable from untrusted networks (public-facing or accessible to attackers). Check virtual server destination addresses and port configurations.Affected if Virtual servers with HTTP/2 profiles are exposed to untrusted network segments or the internet.
The environment is affected if F5 BIG-IP is deployed with any virtual server that has an HTTP/2 profile configured and is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.4.31.7.182.2.3
Apply the vendor patch when released; until then, consider disabling HTTP/2 profiles on virtual servers if not required, or implement aggressive rate limiting on the upstream edge as a temporary measure.
Fix this in Big Ip Next Cloud Native Network Functions
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-59762 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data