CVE-2025-52960: Junos OS: SRX Series and MX Series: Receipt of specific SIP packets in a high utilization situation causes a flowd/mspmand crash
A Buffer Copy without Checking Size of Input vulnerability in the
Session Initialization Protocol (SIP) ALG of Juniper Networks Junos OS on MX Series and SRX Series allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS).
When memory utilization is high, and specific SIP packets are received, flowd/mspmand crashes. While the system recovers automatically, the disruption can significantly impact service stability. Continuous receipt of these specific SIP packets, while high utilization is present, will cause a sustained DoS condition. The utilization is outside the attackers control, so they would not be able to deterministically exploit this. This issue affects Junos OS on SRX Series and MX Series:
All versions before 22.4R3-S7, from 23.2 before 23.2R2-S4, from 23.4 before 23.4R2-S5, from 24.2 before 24.2R2.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-52960?
CVE-2025-52960 has been classified as a high severity vulnerability due to its potential to cause a Denial of Service (DoS) on affected systems.
How do I fix CVE-2025-52960?
To fix CVE-2025-52960, update your Junos OS to a version that is not vulnerable, specifically versions 22.4R3-S7 or later.
What systems are affected by CVE-2025-52960?
CVE-2025-52960 affects Juniper Networks Junos OS on MX Series and SRX Series devices.
What kind of attack can exploit CVE-2025-52960?
An unauthenticated, network-based attacker can exploit CVE-2025-52960 to cause a Denial of Service.
Is there a workaround for CVE-2025-52960?
Currently, there are no documented workarounds for CVE-2025-52960; the recommended action is to apply available patches.