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

CVE-2025-48008

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 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 TCP profile with Multipath TCP (MPTCP) enabled is configured on a virtual server, undisclosed traffic along with conditions beyond the attacker's control 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

This is a denial-of-service vulnerability in F5 BIG-IP where enabling Multipath TCP (MPTCP) on a TCP profile attached to a virtual server can cause the Traffic Management Microkernel (TMM) to terminate. The trigger involves undisclosed traffic patterns combined with conditions not fully under attacker control, making exploitation unreliable.

MitigationDisable MPTCP on affected TCP profiles if not required, or update to a patched version when available. Inventory all virtual servers using MPTCP-enabled TCP profiles to determine exposure.

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 Service Proxy For KubernetesApplication
Affected:>= 1.7.0, <= 1.9.2
Big Ip Access Policy ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6

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. Check the F5 BIG-IP version
    Run 'tmsh show sys version' or view the version in the web UI under Device Management > Overview. Compare the installed version number against the affected ranges: 1.1.0-1.4.1 for Next Cloud Native, 1.7.0-1.9.2 for Next Service Proxy, 15.1.0 to <15.1.10.8 or 16.1.0 to <16.1.6 for traditional BIG-IP modules.
    Affected if The installed version falls within any of the listed affected version ranges.
  2. Identify TCP profiles with MPTCP enabled
    Run 'tmsh list ltm profile tcp all-properties' and look for 'multipath enabled' set to yes, or use the web UI to navigate to Local Traffic > Profiles > TCP and inspect each profile for the MPTCP setting.
    Affected if Any TCP profile has Multipath TCP (MPTCP) explicitly enabled.
  3. Find virtual servers using MPTCP-enabled profiles
    Run 'tmsh list ltm virtual all' and cross-reference the 'profile' or 'profiles' value with the MPTCP-enabled TCP profiles identified in step 2. In the web UI, view each virtual server's properties and check the TCP profile assignment.
    Affected if Any virtual server is assigned an MPTCP-enabled TCP profile.
  4. Verify virtual server is active and processing traffic
    Check the virtual server status using 'tmsh show ltm virtual' or the web UI. An active virtual server with an MPTCP-enabled profile is required for the vulnerability to be triggerable.
    Affected if A virtual server with an MPTCP-enabled TCP profile exists and is in a available or enabled state.

A user is affected if their F5 BIG-IP version is in the affected range AND they have an active virtual server using a TCP profile with MPTCP enabled.

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 or later
Fixed in 15.1.10.816.1.6
Interim mitigation

Disable MPTCP on affected TCP profiles if not required, or update to a patched version when available. Inventory all virtual servers using MPTCP-enabled TCP profiles to determine exposure.

Recommended fix High confidence

Big IP Next CNF: 1.5.0+ | Big IP Next SPfK: 1.10.0+ | Big IP 15.1.x: 15.1.10.8 | Big IP 16.1.x: 16.1.6

  1. 1. Identify the affected F5 BIG-IP product and current version running in your environment
  2. 2. For Big IP Next Cloud Native Network Functions: upgrade to version 1.5.0 or later (the first version after 1.4.1)
  3. 3. For Big IP Next Service Proxy For Kubernetes: upgrade to version 1.10.0 or later (the first version after 1.9.2)
  4. 4. For Big IP APM, AFM, AWAF, Analytics, AAM, and ASM versions 15.1.0-15.1.10.7: upgrade to version 15.1.10.8
  5. 5. For Big IP APM, AFM, AWAF, Analytics, AAM, and ASM versions 16.1.0-16.1.5: upgrade to version 16.1.6
  6. 6. After upgrade, verify that TCP profiles with MPTCP enabled on virtual servers are functioning correctly
  7. 7. Monitor TMM processes to confirm stability after the patch
Caveat Review F5 release notes for any compatibility changes in the target version 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
  • 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-48008 — 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-48008 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