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

CVE-2025-60016

HIGH · 7.5 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 1.4.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
When Diffie-Hellman (DH) group Elliptic Curve Cryptography (ECC) Brainpool curves are configured in an SSL profile's Cipher Rule or Cipher Group, and that profile is applied to a virtual server, 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 confidence

When Diffie-Hellman ECC Brainpool curves are configured in an SSL profile's Cipher Rule or Cipher Group on F5 BIG-IP devices and applied to a virtual server, certain undisclosed traffic patterns can trigger a crash in the Traffic Management Microkernel (TMM), resulting in denial of service.

MitigationRemove or disable Brainpool curves from SSL profile cipher rules and cipher groups until a vendor patch is available, as the vulnerability is triggered by specific traffic handled by profiles using these curves.

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.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
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 checks

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

  1. Identify the F5 BIG-IP Next product and version
    Run 'tmsh show sys version' or check the management console for the exact version of F5 Big Ip Next Cloud Native Network Functions or F5 Big Ip Next Service Proxy For Kubernetes
    Affected if The installed version falls within >= 1.1.0 and < 1.4.0 for Cloud Native Network Functions, or >= 1.7.0 and <= 1.9.2 for Service Proxy For Kubernetes
  2. Locate SSL profiles with Cipher Rules
    Use 'tmsh list ltm cipher rule all' or navigate to Local Traffic > SSL > Cipher Rules in the GUI to list all configured cipher rules
    Affected if Any cipher rule exists that includes Brainpool curves (brainpoolP256r1, brainpoolP384r1, or brainpoolP512r1)
  3. Locate SSL profiles with Cipher Groups
    Use 'tmsh list ltm cipher group all' or navigate to Local Traffic > SSL > Cipher Groups in the GUI to list all configured cipher groups
    Affected if Any cipher group exists that includes Brainpool curves
  4. Check which SSL profiles use Brainpool-enabled cipher rules or groups
    For each identified cipher rule or group, run 'tmsh list ltm cipher rule <name>' or 'tmsh list ltm cipher group <name>' to view the full configuration, noting which SSL profiles reference them
    Affected if An SSL profile references a cipher rule or cipher group that contains Brainpool curves
  5. Verify if affected SSL profiles are assigned to virtual servers
    Run 'tmsh list ltm virtual all' or check the virtual server configuration to see which SSL profiles are attached
    Affected if A virtual server is using an SSL profile that references a cipher rule or cipher group containing Brainpool curves

Your environment is affected if you run a vulnerable version AND have a virtual server with an SSL profile that uses Brainpool curves in its cipher rule or cipher group.

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.

dbcve · scoped
Upgrade available Upgrade to 1.4.0 or later
Fixed in 1.4.0
Interim mitigation

Remove or disable Brainpool curves from SSL profile cipher rules and cipher groups until a vendor patch is available, as the vulnerability is triggered by specific traffic handled by profiles using these curves.

Recommended fix High confidence

BIG-IP Next CNF >= 1.4.0; BIG-IP Next SPK > 1.9.2

  1. 1. Identify all BIG-IP Next Cloud Native Network Functions deployments running versions >= 1.1.0 and < 1.4.0
  2. 2. Identify all BIG-IP Next Service Proxy for Kubernetes deployments running versions >= 1.7.0 and <= 1.9.2
  3. 3. Review SSL profiles on affected systems for Cipher Rules or Cipher Groups using Diffie-Hellman (DH) group Elliptic Curve Cryptography (ECC) Brainpool curves
  4. 4. Upgrade BIG-IP Next Cloud Native Network Functions to version 1.4.0 or later
  5. 5. Upgrade BIG-IP Next Service Proxy for Kubernetes to a version newer than 1.9.2 (e.g., 1.10.0 or later)
  6. 6. After upgrade, verify SSL profiles and virtual servers are functioning correctly
Caveat Review release notes for any breaking changes between current and target versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

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
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60016 — 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-60016 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