CVE-2025-58120
Unknown
Unknown - Not Provided
BaseFortify
Publication date: 2025-10-15
Last updated on: 2025-10-22
Assigner: F5 Networks
Description
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
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 ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs when HTTP/2 Ingress is configured, allowing undisclosed traffic to cause the Traffic Management Microkernel (TMM) to terminate unexpectedly.
How can this vulnerability impact me? :
The vulnerability can cause the Traffic Management Microkernel (TMM) to terminate, which may lead to service disruption or denial of service.
Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70