CVE-2025-61990
TMM vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 17.5.1.3, 17.1.3, 16.1.6.1, 15.1.10.8, 2.1.0-EHF-1, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
When using a multi-bladed platform with more than one blade, 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- F5 BIG-IP
From 17.5.0 · fixed in 17.5.1.3; From 17.1.0 · fixed in 17.1.3; From 16.1.0 · fixed in 16.1.6.1; From 15.1.0 · fixed in 15.1.10.8
- F5 BIG-IP Next SPK
From 2.0.0 · fixed in 2.1.0-EHF-1; From 1.9.0; From 1.8.0; From 1.7.0 · fixed in 1.7.14-EHF-2
- F5 BIG-IP Next CNF
From 2.0.0 · fixed in 2.1.0-EHF-1; From 1.1.0 · fixed in 1.4.0-EHF-3
- F5 BIG-IP Next for Kubernetes
From 2.0.0 · fixed in 2.1.0-EHF-1