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

CVE-2025-61974

HIGH · 7.5 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to after 2.1.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 a client SSL profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization.  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 · high confidence

This is a memory consumption vulnerability in F5 BIG-IP where undisclosed requests to virtual servers with client SSL profiles configured can cause increased memory utilization, potentially leading to denial of service through memory exhaustion.

MitigationApply F5 security patches when available. As a compensating control, remove unused client SSL profiles from virtual servers or implement rate limiting to mitigate unbounded memory growth.

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>= 2.0.0, <= 2.1.0
Big Ip Next For KubernetesApplication
Affected:= 2.0.0= 2.1.0
Big Ip Next Service Proxy For KubernetesApplication
Affected:>= 1.7.0, <= 1.9.2>= 2.0.0, <= 2.0.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
    Determine which F5 BIG-IP Next product is deployed (Cloud Native Network Functions, For Kubernetes, or Service Proxy For Kubernetes) and note its installed version number.
    Affected if The version falls within any of these ranges: 1.1.0-1.4.1, 2.0.0-2.1.0 (CNF); 2.0.0 or 2.1.0 (K8s); 1.7.0-1.9.2 or 2.0.0-2.0.2 (SPK).
  2. Verify virtual servers exist
    Inspect the configuration to determine if any virtual servers are defined in the deployment.
    Affected if Virtual servers are configured in the environment.
  3. Check for client SSL profiles on virtual servers
    Examine the virtual server configurations to identify whether any client SSL profiles are attached or enabled.
    Affected if One or more virtual servers have client SSL profiles configured.
  4. Assess exposure to incoming requests
    Determine if the virtual servers with client SSL profiles are exposed to network traffic or can receive undisclosed requests.
    Affected if The affected virtual servers are reachable by clients or external traffic.

You are affected if your F5 BIG-IP Next product version is within the vulnerable ranges AND you have virtual servers configured with client SSL profiles that can receive traffic.

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 a release after 2.1.0
Interim mitigation

Apply F5 security patches when available. As a compensating control, remove unused client SSL profiles from virtual servers or implement rate limiting to mitigate unbounded memory growth.

Recommended fix Moderate confidence

BIG-IP Next versions 1.4.2+ (for 1.x branch) and 2.1.1+ (for 2.x branch) - check my.f5.com for exact fixed releases

  1. 1. Identify the currently installed F5 BIG-IP Next product version using the management interface or CLI.
  2. 2. Determine the specific product component affected (Cloud Native Network Functions, for Kubernetes, or Service Proxy for Kubernetes).
  3. 3. Navigate to the F5 BIG-IP Next software downloads page on my.f5.com.
  4. 4. Download the fixed release version that supersedes your current vulnerable version.
  5. 5. Review the release notes to confirm the fix addresses CVE-2025-61974 (memory leak in client SSL profile handling).
  6. 6. Follow the standard F5 upgrade procedure for your deployment type (Cloud Native Network Functions, Kubernetes, or Service Proxy for Kubernetes).
  7. 7. After upgrade, verify the new version is running and monitor memory utilization to confirm the leak is resolved.
Caveat Standard upgrade considerations apply - review F5 upgrade documentation for your specific deployment; test in non-production environment first

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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