Junos OS (SRX firewalls)

CVE-2025-60004: Specific BGP EVPN update message causes rpd crash

An Improper Check for Unusual or Exceptional Conditions 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).

Published

ExploitedNot in CISA KEV
Ransomware useNot reportedPer CISA
SeverityHIGHCVSS 4.0 8.7
EPSS0.42%Chance of exploitation in 30 days
Public exploitNot tracked
FixAvailable

Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.

Affected and fixed versions

Product / branchFixed in
Junos OS 23.4R2-S323.4R2-S5 or later
Junos OS 24.2R224.2R2-S1 or later
Junos OS 24.4R124.4R1-S3, 24.4R2 or later
Junos OS Evolved 23.4R2-S2-EVO23.4R2-S5-EVO or later
Junos OS Evolved 24.2R2-EVO24.2R2-S1-EVO or later
Junos OS Evolved 24.4R1-EVO24.4R1-S3-EVO, 24.4R2-EVO or later

Always confirm against the vendor advisory, which lists every fixed hotfix.

What it is

An Improper Check for Unusual or Exceptional Conditions 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 system receives a specific BGP EVPN update message over an established BGP session, this causes an rpd crash and restart.

A BGP EVPN configuration is not necessary to be vulnerable. If peers are not configured to send BGP EVPN updates to a vulnerable device, then this issue can't occur.

This issue affects iBGP and eBGP, over IPv4 and IPv6.

This issue affects: Junos OS: * 23.4 versions from

23.4R2-S3 before 23.4R2-S5, * 24.2 versions from

24.2R2

before 24.2R2-S1, * 24.4 versions before 24.4R1-S3, 24.4R2;

Junos OS Evolved: * 23.4-EVO versions from 23.4R2-S2-EVO before 23.4R2-S5-EVO, * 24.2-EVO versions from 24.2R2-EVO before 24.2R2-S1-EVO, * 24.4-EVO versions before 24.4R1-S3-EVO, 24.4R2-EVO.

Am I affected?

To be exposed to this issue a BGP peering needs to be configured via:

[ protocols bgp ... neighbor ... ]

Workarounds

There are no known workarounds for this issue.

Exploitation

Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

Sources

KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.

Get alerts

A notification when we publish a new analysis or a covered vendor gets a new actively exploited CVE. No account, no email.