CVE-2025-59962

Junos OS and Junos OS Evolved: With BGP sharding enabled, change in indirect next-hop can cause RPD crash

MEDIUM
5.3
CVSS Score
Published: October 9, 2025 at 03:45 PM UTC
Updated: October 18, 2026 at 09:10 PM UTC
3 products affected across 2 vendorsJunosJunos OS EvolvedJunos OS Evolved

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

An Access of Uninitialized Pointer vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved with BGP sharding configured allows an attacker triggering indirect next-hop updates, along with timing outside the attacker's control, to cause rpd to crash and restart, leading to a Denial of Service (DoS). With BGP sharding enabled, triggering route resolution of an indirect next-hop (e.g., an IGP route change over which a BGP route gets resolved), may cause rpd to crash and restart. An attacker causing continuous IGP route churn, resulting in repeated route re-resolution, will increase the likelihood of triggering this issue, leading to a potentially extended DoS condition. This issue affects: Junos OS: * all versions before 21.4R3-S6,  * from 22.1 before 22.1R3-S6,  * from 22.2 before 22.2R3-S3,  * from 22.3 before 22.3R3-S3,  * from 22.4 before 22.4R3,  * from 23.2 before 23.2R2; Junos OS Evolved: * all versions before 22.3R3-S3-EVO,  * from 22.4 before 22.4R3-EVO,  * from 23.2 before 23.2R2-EVO. Versions before Junos OS 21.3R1 and Junos OS Evolved 21.3R1-EVO are unaffected by this issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Vendor states this is fixed in 21.3R1 (unaffected)
Affected range stops below 21.4R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2, so it looks safe — our inference, not a vendor statement
22.3 ≤ v < 22.3R3-S3-EVO22.4 ≤ v < 22.4R3-EVO23.2 ≤ v < 23.2R2-EVO22.322.423.2
Vendor states this is fixed in 21.3R1-EVO (unaffected)
Affected range stops below 22.3R3-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-EVO, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://supportportal.juniper.net/JSA103151

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMjuniper
Attack Vector
ADJACENT_NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-824

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card