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

CVE-2025-54479

HIGH · 7.5 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 15.1.10.8 / 16.1.6.1 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 classification profile is configured on a virtual server without an HTTP or HTTP/2 profile, undisclosed requests 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 · high confidence

In F5 BIG-IP, when a classification profile is attached to a virtual server without an accompanying HTTP or HTTP/2 profile, specific undisclosed requests can trigger a crash in the Traffic Management Microkernel (TMM), resulting in denial of service.

MitigationEnsure all virtual servers with classification profiles also have HTTP or HTTP/2 profiles configured to prevent TMM termination from malformed requests.

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= 2.0.0= 2.0.1= 2.0.2= 2.1.0
Big Ip Next For KubernetesApplication
Affected:= 2.0.0= 2.1.0
Big Ip Policy Enforcement ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3= 17.5.0

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 installed F5 product and version
    Use the command 'tmsh show sys version' or check the management console for the exact BIG-IP Next or Policy Enforcement Manager version
    Affected if The installed version falls within the ranges: Big Ip Next Cloud Native (1.1.0-1.4.0, 2.0.0-2.0.2, 2.1.0), Big Ip Next For Kubernetes (2.0.0, 2.1.0), Policy Enforcement Manager (15.1.0-15.1.10.7, 16.1.0-16.1.6.0, 17.1.0-17.2.x, 17.5.0)
  2. List all virtual servers with classification profiles
    Use 'tmsh list ltm virtual' combined with profile classification or check the GUI under Virtual Servers > Profiles to identify which virtual servers have a classification profile applied
    Affected if Any virtual server has a classification profile attached
  3. Verify HTTP or HTTP/2 profile presence on virtual servers
    For each virtual server with a classification profile, examine the profile configuration using 'tmsh list ltm virtual <name>' or the GUI to confirm whether an HTTP or HTTP/2 profile is also assigned
    Affected if A virtual server has a classification profile but NO HTTP or HTTP/2 profile configured
  4. Confirm the vulnerability condition
    Cross-reference the findings: identify virtual servers where classification is present but HTTP/HTTP2 is absent, creating the crash condition
    Affected if At least one virtual server has a classification profile without an accompanying HTTP or HTTP/2 profile

You are affected if your F5 BIG-IP version is within the affected ranges AND you have virtual servers with classification profiles that lack HTTP or HTTP/2 profiles configured.

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 15.1.10.8 / 16.1.6.1 / 17.1.3 or later
Fixed in 15.1.10.816.1.6.117.1.3
Interim mitigation

Ensure all virtual servers with classification profiles also have HTTP or HTTP/2 profiles configured to prevent TMM termination from malformed requests.

Recommended fix Moderate confidence

Big Ip Next Cloud Native Network Functions: 1.4.1+ or 2.0.3+; Big Ip Next For Kubernetes: 2.1.1+; Big Ip Policy Enforcement Manager: 15.1.10.8+, 16.1.6.1+, 17.1.3+, or 17.6.0+

  1. 1. Identify the exact deployed version of Big Ip Next Cloud Native Network Functions, Big Ip Next For Kubernetes, or Big Ip Policy Enforcement Manager using the command line interface or management console.
  2. 2. For Big Ip Next Cloud Native Network Functions: Upgrade to version 1.4.1 or later, or version 2.0.3 or later.
  3. 3. For Big Ip Next For Kubernetes: Upgrade to version 2.1.1 or later.
  4. 4. For Big Ip Policy Enforcement Manager: Upgrade to version 15.1.10.8 or later, 16.1.6.1 or later, 17.1.3 or later, or 17.6.0 or later (if available).
  5. 5. After upgrading, verify that classification profiles are properly configured with associated HTTP or HTTP/2 profiles on virtual servers to prevent recurrence.
  6. 6. Test the configuration in a staging environment before deploying to production.
Caveat Review F5 release notes for each target version to check for configuration or behavioral changes that may affect existing deployments

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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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