CVE-2025-58120
published 2025-10-15CVE-2025-58120: When HTTP/2 Ingress is configured, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have…
PriorityP341high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
0.32%
24.4th percentile
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.
Affected
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| f5 | big-ip_next_cloud-native_network_functions | — | — |
| f5 | big-ip_next_cloud-native_network_functions | 1.1.0 – 1.4.1 | — |
| f5 | big-ip_next_cnf | — | — |
| f5 | big-ip_next_cnf | >= 1.1.0 < * | * |
| f5 | big-ip_next_cnf | >= 2.0.0 < 2.0.1 | 2.0.1 |
| f5 | big-ip_next_for_kubernetes | — | — |
| f5 | big-ip_next_for_kubernetes | — | — |
| f5 | big-ip_next_for_kubernetes | >= 2.0.0 < 2.1.0 | 2.1.0 |
| f5 | big-ip_next_service_proxy_for_kubernetes | — | — |
| f5 | big-ip_next_service_proxy_for_kubernetes | — | — |
| f5 | big-ip_next_service_proxy_for_kubernetes | — | — |
| f5 | big-ip_next_service_proxy_for_kubernetes | >= 1.7.0 < 1.7.14 | 1.7.14 |
| f5 | big-ip_next_spk | >= 1.7.0 < * | * |
| f5 | big-ip_next_spk | >= 1.8.0 < * | * |
| f5 | big-ip_next_spk | >= 1.9.0 < * | * |
| f5 | big-ip_next_spk | >= 2.0.0 < 2.0.1 | 2.0.1 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv4.08.7HIGHCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-jg4r-5fpx-73gm: When HTTP/2 Ingress is configured, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate
ghsa_unreviewed·2025-10-15
CVE-2025-58120 [HIGH] CWE-476 GHSA-jg4r-5fpx-73gm: When HTTP/2 Ingress is configured, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate
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.
F5
CVE-2025-58120: When HTTP/2 Ingress is configured, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate
vendor_f5·2025-10-15·CVSS 7.5
CVE-2025-58120 [HIGH] CWE-476 CVE-2025-58120: When HTTP/2 Ingress is configured, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate
CVE-2025-58120: When HTTP/2 Ingress is configured, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate
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.
Affected Products: BIG-IP Next CNF, Big-Ip Next For Kubernetes, Big-Ip Next Service Proxy For Kubernetes
Affected Versions: 1.1.0 - 1.4.1; 1.7.0 - 1.7.14; 1.7.14; 2.0.0
F5 Advisory Articles: K000156623
F5 References: https://my.f5.com/manage/s/article/K000156623
No detection rules found.
No public exploits indexed.
2025-10-15
Published