dbcve.org
Big Ip Next Cloud Native Network FunctionsApplication · F5

CVE-2025-55670

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to after 1.9.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
On BIG-IP Next CNF, BIG-IP Next SPK, and BIG-IP Next for Kubernetes systems, repeated undisclosed API calls 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 confidence

On BIG-IP Next CNF, SPK, and Kubernetes variants, an undisclosed API endpoint allows remote attackers to cause denial of service by repeatedly sending specific API requests, which causes the Traffic Management Microkernel (TMM) to terminate unexpectedly.

MitigationApply F5-provided patches for BIG-IP Next when available; until then, restrict API access through network segmentation or firewall rules to limit exposure to untrusted sources.

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
Affected:>= 1.1.0, <= 1.4.1
Big Ip Next For KubernetesApplication
Affected:= 2.0.0
Big Ip Next Service Proxy For KubernetesApplication
Affected:>= 1.7.0, <= 1.9.2

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the F5 product variant
    Determine which F5 BIG-IP Next variant is deployed in your environment: Cloud Native Network Functions (CNF), Service Proxy for Kubernetes (SPK), or BIG-IP Next for Kubernetes. Check the product documentation, deployment manifests, or running containers/pods for identifiers.
    Affected if The product is any of these three variants (CNF, SPK, or BIG-IP Next for Kubernetes)
  2. Check BIG-IP Next CNF version
    For CNF deployments, run 'kubectl get bigipnextcnf -A' or check the installed CNF operator version using 'kubectl get pods -A | grep bigipnext'. Compare the version against the affected range 1.1.0 to 1.4.1.
    Affected if Version is >= 1.1.0 and <= 1.4.1
  3. Check BIG-IP Next for Kubernetes version
    For Kubernetes deployments, identify the BIG-IP Next Central Manager or BIG-IP Next instance version using 'kubectl get pods -A' or check the product-specific CRDs. Compare against affected version 2.0.0.
    Affected if Version is exactly 2.0.0
  4. Check SPK version
    For SPK deployments, check the installed SPK version via kubectl or the SPK deployment documentation. Compare against affected range 1.7.0 to 1.9.2.
    Affected if Version is >= 1.7.0 and <= 1.9.2
  5. Assess API exposure to untrusted networks
    Review network policies, firewall rules, and ingress configurations to determine if the BIG-IP Next API services are accessible from untrusted network sources. Check if the API listener is bound to non-internal IP addresses or exposed via load balancers accessible from the internet.
    Affected if API services are exposed to networks that are not explicitly trusted or internal

Your environment is affected if you are running any of the affected product variants within the specified version ranges AND the API endpoint is accessible to untrusted sources, regardless of version if exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.9.2
Interim mitigation

Apply F5-provided patches for BIG-IP Next when available; until then, restrict API access through network segmentation or firewall rules to limit exposure to untrusted sources.

Fix this in Big Ip Next Cloud Native Network Functions Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55670 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55670 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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