CVE-2025-58120

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.
References
Link Resource
https://my.f5.com/manage/s/article/K000156623 Vendor Advisory
Configurations

Configuration 1 (hide)

OR cpe:2.3:a:f5:big-ip_next_cloud-native_network_functions:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_next_cloud-native_network_functions:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_next_for_kubernetes:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_next_service_proxy_for_kubernetes:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_next_service_proxy_for_kubernetes:1.7.14:-:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_next_service_proxy_for_kubernetes:2.0.0:*:*:*:*:*:*:*

History

18 Oct 2026, 21:10

Type Values Removed Values Added
Summary
  • (es) Cuando HTTP/2 Ingress está configurado, el tráfico no revelado puede causar que el Microkernel de Gestión de Tráfico (TMM) se cierre. Nota: Las versiones de software que han alcanzado el Fin del Soporte Técnico (EoTS) no se evalúan.

Information

Published : 2025-10-15 14:15

Updated : 2026-10-18 21:10


NVD link : CVE-2025-58120

Mitre link : CVE-2025-58120

CVE.ORG link : CVE-2025-58120


JSON object : View

Products Affected

f5

  • big-ip_next_service_proxy_for_kubernetes
  • big-ip_next_for_kubernetes
  • big-ip_next_cloud-native_network_functions
CWE
CWE-476

NULL Pointer Dereference