CVE-2025-60003

Junos OS and Junos OS Evolved: BGP update with a set of specific attributes causes rpd crash

HIGH
7.5
CVSS Score
Published: January 15, 2026 at 08:15 PM UTC
Updated: June 17, 2026 at 09:49 AM 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
HIGH7.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

A Buffer Over-read 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 an affected device receives a BGP update with a set of specific optional transitive attributes over an established peering session, rpd will crash and restart when attempting to advertise the received information to another peer. This issue can only happen if one or both of the BGP peers of the receiving session are non-4-byte-AS capable as determined from the advertised capabilities during BGP session establishment. Junos OS and Junos OS Evolved default behavior is 4-byte-AS capable unless this has been specifically disabled by configuring: [ protocols bgp ... disable-4byte-as ] Established BGP sessions can be checked by executing: show bgp neighbor <IP address> | match "4 byte AS" This issue affects: Junos OS: * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S5, * 23.4 versions before 23.4R2-S6, * 24.2 versions before 24.2R2-S2, * 24.4 versions before 24.4R2; Junos OS Evolved: * all versions before 22.4R3-S8-EVO, * 23.2 versions before 23.2R2-S5-EVO, * 23.4 versions before 23.4R2-S6-EVO, * 24.2 versions before 24.2R2-S2-EVO, * 24.4 versions before 24.4R2-EVO.

Affected

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

Affected range stops below 22.4R3-S8, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4R2-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.2R2-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.4R2, so it looks safe — our inference, not a vendor statement
v < 22.4R3-S8-EVO23.2 ≤ v < 23.2R2-S5-EVO23.4 ≤ v < 23.4R2-S6-EVO24.2 ≤ v < 24.2R2-S2-EVO24.4 ≤ v < 24.4R2-EVO23.223.424.224.4
Affected range stops below 22.4R3-S8-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-S5-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4R2-S6-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.2R2-S2-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.4R2-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:

References (2)

Vendor Advisory
Source: cverecord
https://supportportal.juniper.net/
Vendor Advisory
Source: cverecord
https://kb.juniper.net/JSA103166

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

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

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-126

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