CVE-2025-55670

BIG-IP Next (CNF, SPK, and Kubernetes) vulnerability

MEDIUM
6.5
CVSS Score
Published: October 15, 2025 at 01:55 PM UTC
Updated: October 18, 2026 at 09:10 PM UTC
3 products affected across 1 vendorBig IP Next Cloud Native Network FunctionsBig IP Next Service Proxy for KubernetesBIG-IP Next for Kubernetes

Using BIG-IP Next SPK by F5?

Get instant alerts when new vulnerabilities affect BIG-IP Next SPK - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.1.0 ≤ v ≤ 1.4.11.1.0
Vendor states this is fixed in 2.0.0 (unaffected)
Affected range stops below 2.1.0, so it looks safe — our inference, not a vendor statement
1.7.0 ≤ v ≤ 1.9.21.7.0
Vendor states this is fixed in 2.0.0 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

Vendor Advisory
Source: cverecord
https://my.f5.com/manage/s/article/K000154614

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMf5
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card