CVE-2025-52953: Juniper Networks Junos OS · Expected Behavior Violation
Affects Juniper Networks Junos OSSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Juniper Networks Junos OS | Affected
| Fixed in– |
AI-suggested
European organizations should prioritize upgrading Juniper devices to fixed versions as listed by Juniper Networks, ensuring deployment of patches for both Junos OS and Junos OS Evolved. Network administrators should audit BGP peer configurations to restrict adjacency to trusted and authenticated peers only, employing BGP session authentication mechanisms such as TCP MD5 signatures or TCP-AO where supported. Implement strict network segmentation and access control lists (ACLs) to limit which devices can send BGP UPDATE packets to routing devices. Monitoring and alerting on abnormal BGP session resets and unusual BGP UPDATE traffic patterns can provide early detection of exploitation attempts. Additionally, organizations should consider deploying BGP session protection features and rate limiting on BGP control plane traffic to mitigate the impact of repeated malicious packets. Regular vulnerability scanning and configuration reviews should be conducted to ensure no legacy or unsupported versions remain in production. Finally, incident response plans should include procedures for rapid remediation of routing disruptions caused by this vulnerability.
Description
An Expected Behavior Violation vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker sending a valid BGP UPDATE packet to cause a BGP session reset, resulting in a Denial of Service (DoS). Continuous receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue affects iBGP and eBGP and both IPv4 and IPv6 are affected by this vulnerability. This issue affects Junos OS: * All versions before 21.2R3-S9, * from 21.4 before 21.4R3-S11, * from 22.2 before 22.2R3-S7, * from 22.4 before 22.4R3-S7, * from 23.2 before 23.2R2-S4, * from 23.4 before 23.4R2-S4, * from 24.2 before 24.2R2, * from 24.4 before 24.4R1-S3, 24.4R2 Junos OS Evolved: * All versions before 22.2R3-S7-EVO, * from 22.4-EVO before 22.4R3-S7-EVO, * from 23.2-EVO before 23.2R2-S4-EVO, * from 23.4-EVO before 23.4R2-S4-EVO, * from 24.2-EVO before 24.2R2-EVO, * from 24.4-EVO before 24.4R1-S3-EVO, 24.4R2-EVO.