CVE-2025-52958: Junos OS and Junos OS Evolved: When route validation is enabled, BGP connection establishment failure causes RPD crash

Published Jul 11, 2025
·
Updated

A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS).On all Junos OS and Junos OS Evolved devices, when route validation is enabled, a rare condition during BGP initial session establishment can lead to an rpd crash and restart. This occurs specifically when the connection request fails during error-handling scenario.

Continued session establishment failures leads to a sustained DoS condition.

This issue affects Junos OS:

All versions before 22.2R3-S6, from 22.4 before 22.4R3-S6, from 23.2 before 23.2R2-S3, from 23.4 before 23.4R2-S4, from 24.2 before 24.2R2;

Junos OS Evolved: All versions before 22.2R3-S6-EVO, from 22.4 before 22.4R3-S6-EVO, from 23.2 before 23.2R2-S3-EVO, from 23.4 before 23.4R2-S4-EVO, from 24.2 before 24.2R2-EVO.

Affected Software

93 affected components
Juniper Networks Junos OS<22.2R3-S6, >=undefined, >=undefined, >=undefined, >=undefined
Juniper Networks Junos OS Evolved<22.2R3-S6-EVO, >=undefined, >=undefined, >=undefined, >=undefined
Juniper Junos<22.2
Juniper Junos=22.2
Juniper Junos=22.2-r1
Juniper Junos=22.2-r1-s1
Juniper Junos=22.2-r1-s2
Juniper Junos=22.2-r2
Juniper Junos=22.2-r2-s1
Juniper Junos=22.2-r2-s2
Juniper Junos=22.2-r3
Juniper Junos=22.2-r3-s1
Juniper Junos=22.2-r3-s2
Juniper Junos=22.2-r3-s3
Juniper Junos=22.2-r3-s4
Juniper Junos=22.2-r3-s5
Juniper Junos=22.4
Juniper Junos=22.4-r1
Juniper Junos=22.4-r1-s1
Juniper Junos=22.4-r1-s2
Juniper Junos=22.4-r2
Juniper Junos=22.4-r2-s1
Juniper Junos=22.4-r2-s2
Juniper Junos=22.4-r3
Juniper Junos=22.4-r3-s1
Juniper Junos=22.4-r3-s2
Juniper Junos=22.4-r3-s3
Juniper Junos=22.4-r3-s4
Juniper Junos=22.4-r3-s5
Juniper Junos=23.2
Juniper Junos=23.2-r1
Juniper Junos=23.2-r1-s1
Juniper Junos=23.2-r1-s2
Juniper Junos=23.2-r2
Juniper Junos=23.2-r2-s1
Juniper Junos=23.2-r2-s2
Juniper Junos=23.4
Juniper Junos=23.4-r1
Juniper Junos=23.4-r1-s1
Juniper Junos=23.4-r1-s2
Juniper Junos=23.4-r2
Juniper Junos=23.4-r2-s1
Juniper Junos=23.4-r2-s2
Juniper Junos=23.4-r2-s3
Juniper Junos=24.2
Juniper Junos=24.2-r1
Juniper Junos=24.2-r1-s1
Juniper Junos=24.2-r1-s2
Juniper Junos OS Evolved<22.2
Juniper Junos OS Evolved=22.2
Juniper Junos OS Evolved=22.2-r1
Juniper Junos OS Evolved=22.2-r1-s1
Juniper Junos OS Evolved=22.2-r1-s2
Juniper Junos OS Evolved=22.2-r2
Juniper Junos OS Evolved=22.2-r2-s1
Juniper Junos OS Evolved=22.2-r2-s2
Juniper Junos OS Evolved=22.2-r3
Juniper Junos OS Evolved=22.2-r3-s1
Juniper Junos OS Evolved=22.2-r3-s2
Juniper Junos OS Evolved=22.2-r3-s3
Juniper Junos OS Evolved=22.2-r3-s4
Juniper Junos OS Evolved=22.2-r3-s5
Juniper Junos OS Evolved=22.4
Juniper Junos OS Evolved=22.4-r1
Juniper Junos OS Evolved=22.4-r1-s1
Juniper Junos OS Evolved=22.4-r1-s2
Juniper Junos OS Evolved=22.4-r2
Juniper Junos OS Evolved=22.4-r2-s1
Juniper Junos OS Evolved=22.4-r2-s2
Juniper Junos OS Evolved=22.4-r3
Juniper Junos OS Evolved=22.4-r3-s1
Juniper Junos OS Evolved=22.4-r3-s2
Juniper Junos OS Evolved=22.4-r3-s3
Juniper Junos OS Evolved=22.4-r3-s4
Juniper Junos OS Evolved=22.4-r3-s5
Juniper Junos OS Evolved=23.2
Juniper Junos OS Evolved=23.2-r1
Juniper Junos OS Evolved=23.2-r1-s1
Juniper Junos OS Evolved=23.2-r1-s2
Juniper Junos OS Evolved=23.2-r2
Juniper Junos OS Evolved=23.2-r2-s1
Juniper Junos OS Evolved=23.2-r2-s2
Juniper Junos OS Evolved=23.4
Juniper Junos OS Evolved=23.4-r1
Juniper Junos OS Evolved=23.4-r1-s1
Juniper Junos OS Evolved=23.4-r1-s2
Juniper Junos OS Evolved=23.4-r2
Juniper Junos OS Evolved=23.4-r2-s1
Juniper Junos OS Evolved=23.4-r2-s2
Juniper Junos OS Evolved=23.4-r2-s3
Juniper Junos OS Evolved=24.2
Juniper Junos OS Evolved=24.2-r1
Juniper Junos OS Evolved=24.2-r1-s2

Remediation

Information

The following software releases have been updated to resolve this specific issue: Junos OS Evolved: 22.2R3-S6-EVO, 22.4R3-S6-EVO, 23.2R2-S3-EVO, 23.4R2-S4-EVO, 24.2R2-EVO, 24.4R1-EVO, and all subsequent releases. Junos OS: 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S4, 24.2R2, 24.4R1, and all subsequent releases.

Event History

Jul 11, 2025
CVE Published
via MITRE·02:43 PM
Data Sourced
via MITRE·02:43 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-52958?

CVE-2025-52958 is classified as a High severity vulnerability due to its potential to cause a Denial of Service (DoS) with adjacent, unauthenticated access.

2

How do I fix CVE-2025-52958?

To fix CVE-2025-52958, upgrade to Junos OS versions 22.2R3-S7 or later and Junos OS Evolved versions 22.2R3-S7-EVO or later.

3

Who is affected by CVE-2025-52958?

CVE-2025-52958 affects all devices running vulnerable versions of Juniper Networks Junos OS and Junos OS Evolved.

4

What type of attack does CVE-2025-52958 facilitate?

CVE-2025-52958 facilitates a Denial of Service (DoS) attack through a reachable assertion vulnerability in the routing protocol daemon.

5

When was CVE-2025-52958 published?

CVE-2025-52958 was published on October 9, 2025.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203