BaseFortify

Publication date: 2025-10-15

Last updated on: 2025-10-22

Assigner: F5 Networks

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-15

Last Modified

2025-10-22

Generated

2026-07-06

AI Q&A

2025-10-15

EPSS Evaluated

2026-07-05

NVD

CVE-2025-58120

Affected Vendors & Products

Vendor	Product	Version / Range
f5	big-ip_next_cloud-native_network_functions	From 1.1.0 (inc) to 1.4.1 (inc)
f5	big-ip_next_cloud-native_network_functions	2.0.0
f5	big-ip_next_for_kubernetes	2.0.0
f5	big-ip_next_service_proxy_for_kubernetes	From 1.7.0 (inc) to 1.7.14 (exc)
f5	big-ip_next_service_proxy_for_kubernetes	1.7.14
f5	big-ip_next_service_proxy_for_kubernetes	2.0.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-476	The product dereferences a pointer that it expects to be valid but is NULL.

Attack-Flow Graph

Executive Summary

This vulnerability occurs when HTTP/2 Ingress is configured, allowing undisclosed traffic to cause the Traffic Management Microkernel (TMM) to terminate unexpectedly.

Impact Analysis

The vulnerability can cause the Traffic Management Microkernel (TMM) to terminate, which may lead to service disruption or denial of service.

Hi! I’m here to help you understand CVE-2025-58120. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70