Big Ip Next Cloud Native Network FunctionsApplication · F5
CVE-2025-58120
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 HTTP/2 Ingress is configured, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
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 denial-of-service vulnerability in F5 products where specially crafted undisclosed HTTP/2 Ingress traffic causes the Traffic Management Microkernel (TMM) to terminate, resulting in service disruption. The vulnerability has a CVSS score of 7.5 (High), indicating significant availability impact.
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.1= 2.0.0
Big Ip Next For KubernetesApplication
= 2.0.0
Big Ip Next Service Proxy For KubernetesApplication
>= 1.7.0, < 1.7.14= 1.7.14= 2.0.0CVSS 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 the F5 productDetermine which F5 Big Ip Next product is deployed in your environment: Cloud Native Network Functions (CNF), for Kubernetes, or Service Proxy for KubernetesAffected if Any of the three affected product types are in use
-
Check installed version for Big Ip Next CNFRun the command to display the Big Ip Next Cloud Native Network Functions versionAffected if The installed version is >= 1.1.0 and <= 1.4.1, or is exactly 2.0.0
-
Check installed version for Big Ip Next for KubernetesRun the command to display the Big Ip Next for Kubernetes versionAffected if The installed version is exactly 2.0.0
-
Check installed version for Service Proxy for KubernetesRun the command to display the Big Ip Next Service Proxy for Kubernetes versionAffected if The installed version is >= 1.7.0 and < 1.7.14, is exactly 1.7.14, or is exactly 2.0.0
-
Verify HTTP/2 Ingress configurationInspect the Ingress resource definitions or proxy configuration to confirm HTTP/2 is enabled for inbound trafficAffected if HTTP/2 Ingress traffic is allowed and the product version falls within the affected ranges
You are affected if you are running any of the affected F5 product versions AND HTTP/2 Ingress traffic is enabled in your environment.
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.7.14
Update to a non-EoTS version that includes the fix for this vulnerability, or review and modify HTTP/2 Ingress configuration settings to mitigate the issue until a patch can be applied.
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-2025-58120 — 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-2025-58120 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