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

High 8.7 Published Updated

An unauthenticated attacker can crash the routing daemon via a crafted BGP update if 4-byte AS support is disabled, causing denial of service.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-60003?

CVE-2025-60003 is a high-severity memory corruption vulnerability in Juniper Junos, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-126

Which versions are affected by CVE-2025-60003?

It affects 2 products.

Products include Juniper Junos, Juniper Junos Os Evolved.

How do I fix CVE-2025-60003?

No fix has been published for CVE-2025-60003 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2025-60003 being exploited?

There is no known exploitation of CVE-2025-60003 in the wild and no public exploit code.

All Juniper Junos vulnerabilities

Sources

Also known as GHSA-crj7-7vc6-g6g3.

Is CVE-2025-60003 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free