Skip to main content
VulnerabilityPublished Updated

CVE-2025-52960: Juniper Networks Junos OS · Classic Buffer Overflow

Affects Juniper Networks Junos OSSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Juniper Networks Junos OSAffected
  • =0
  • =23.2
  • =23.4
  • =24.2
Fixed in–

AI-suggested

European organizations should prioritize patching affected Junos OS devices to versions 22.4R3-S7 or later, 23.2R2-S4 or later, 23.4R2-S5 or later, and 24.2R2 or later as applicable. Network administrators should monitor memory utilization on MX and SRX devices to identify periods of high load that could increase vulnerability exposure. Implementing rate limiting or filtering of SIP traffic at network edges can reduce the likelihood of receiving malicious SIP packets. Deploying intrusion detection/prevention systems (IDS/IPS) with signatures tuned to detect anomalous SIP packet patterns may help detect exploitation attempts. Network segmentation to isolate critical Junos OS devices from untrusted networks can reduce attack surface. Regularly reviewing device logs for flowd/mspmand crashes or SIP-related anomalies can provide early warning signs. Organizations should also engage with Juniper support for any additional recommended mitigations or hotfixes. Finally, maintaining an up-to-date asset inventory of Junos OS devices and their versions will aid in targeted remediation efforts.

Description

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.

References

Community reviews

Loading reviews…