Skip to main content
CVE-2025-52964VulnerabilityPublished Updated

CVE-2025-52964: Juniper Networks Junos OS · Reachable Assertion

Affects Juniper Networks Junos OSSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jul 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Juniper Networks Junos OSAffected
  • =0
  • =22.3
  • =22.4
  • =23.2
  • =23.4
  • =22.1
  • =22.2
Fixed in–

AI-suggested

1. Immediate patching: Organizations should upgrade Junos OS and Junos OS Evolved to the fixed versions listed by Juniper (e.g., 21.4R3-S7 or later) as soon as possible to eliminate the vulnerability. 2. Configuration review: Disable BGP multipath with the "pause-computation-during-churn" feature if it is not essential, as this configuration is required to trigger the vulnerability. 3. BGP peer security: Restrict BGP peering to trusted and authenticated peers only, using strong authentication mechanisms such as TCP MD5 signatures or TCP-AO to prevent unauthorized BGP session establishment. 4. Network segmentation: Isolate BGP routers from untrusted networks and limit access to BGP sessions to reduce the risk of malicious BGP UPDATE injection. 5. Monitoring and alerting: Implement monitoring on rpd process stability and BGP session anomalies to detect potential exploitation attempts early. 6. Incident response readiness: Prepare response plans for potential DoS events impacting routing to minimize downtime and impact. 7. Vendor advisories: Stay updated with Juniper security advisories for any new patches or mitigations related to this vulnerability.

Description

A Reachable Assertion vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When the device receives a specific BGP UPDATE packet, the rpd crashes and restarts. Continuous receipt of this specific packet will cause a sustained DoS condition. For the issue to occur, BGP multipath with "pause-computation-during-churn" must be configured on the device, and the attacker must send the paths via a BGP UPDATE from a established BGP peer. This issue affects: Junos OS: * All versions before 21.4R3-S7, * from 22.3 before 22.3R3-S3, * from 22.4 before 22.4R3-S5, * from 23.2 before 23.2R2, * from 23.4 before 23.4R2. Junos OS Evolved: * All versions before 21.4R3-S7-EVO, * from 22.3 before 22.3R3-S3-EVO, * from 22.4 before 22.4R3-S5-EVO, * from 23.2 before 23.2R2-EVO, * from 23.4 before 23.4R2-EVO.

References

Community reviews

Loading reviews…