F5 BIG-IP/BIG-IP Next SPK prior 16.1.5/17.1.2 Traffic Management Microkernel denial of service

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in F5 BIG-IP and BIG-IP Next SPK. Affected by this issue is some unknown functionality of the component Traffic Management Microkernel. This manipulation causes denial of service. This vulnerability is tracked as CVE-2025-22846. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in F5 BIG-IP and BIG-IP Next SPK. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Traffic Management Microkernel. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
When SIP Session and Router ALG profiles are configured on a Message Routing type virtual server, 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.
The advisory is shared at my.f5.com. This vulnerability is known as CVE-2025-22846 since 01/22/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 215018 (F5 Networks BIG-IP : BIG-IP SIP ALG vulnerability (K000139780)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 16.1.5 or 17.1.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (215018). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://f5.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 215018
Nessus Name: F5 Networks BIG-IP : BIG-IP SIP ALG vulnerability (K000139780)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: BIG-IP/BIG-IP Next SPK 16.1.5/17.1.2
Timeline
01/22/2025 🔍02/05/2025 🔍
02/05/2025 🔍
09/10/2025 🔍
Sources
Vendor: f5.comAdvisory: K000139780
Status: Confirmed
CVE: CVE-2025-22846 (🔍)
GCVE (CVE): GCVE-0-2025-22846
GCVE (VulDB): GCVE-100-294757
Entry
Created: 02/05/2025 18:50Updated: 09/10/2025 18:47
Changes: 02/05/2025 18:50 (76), 02/06/2025 00:03 (2), 09/10/2025 18:47 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.