CVE Intelligence
High Logic error

CVE-2025-60004 — Junos OS and Junos OS Evolved: 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). 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.

Published Oct 9, 2025 · Updated Oct 18, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: juniper

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.42%
ahead of 35% of scored CVEs · Oct 18, 2026
Affects
Juniper Networks
Junos and 2 more
CVSS base
7.5
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Juniper Networks Junos, Juniper Networks Junos OS, Juniper Networks Junos Os Evolved).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Juniper Networks Junos version 23.4-r2-s4version 24.2-r2version 24.4version 24.4-r1version 24.4-r1-s2version 24.4-r2version 23.4-r2-s3 Vulnerable NIST National Vulnerability Database
Juniper Networks Junos OS ≥ 23.4R2-S3 and < 23.4R2-S5≥ 24.2R2 and < 24.2R2-S1≥ 24.4R1 and < 24.4R1-S3, 24.4R2 Vulnerable CVE Program (cve.org) e CISA ADP
Juniper Networks Junos Os Evolved ≥ 24.4R1-EVO and < 24.4R1-S3-EVO, 24.4R2-EVO≥ 24.2R2-EVO and < 24.2R2-S1-EVO≥ 23.4R2-S2-EVO and < 23.4R2-S5-EVO Vulnerable CVE Program (cve.org) e CISA ADP
Juniper Networks Junos Os Evolved version 24.4-r2version 24.4-r1-s2version 24.4-r1version 24.4version 24.2-r2version 23.4-r2-s4version 23.4-r2-s3version 23.4-r2-s2 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.7 CVSS 4.0 High — — sirt@juniper.net via NIST National Vulnerability Database
8.7 CVSS 4.0 High — — juniper via CVE Program (cve.org) e CISA ADP
7.5 CVSS 3.1 High 3.9 3.6 sirt@juniper.net via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 3.1 High — — juniper via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: sirt@juniper.net)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-754 · Improper Check for Unusual or Exceptional Conditions

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · juniper networks/junos os, juniper networks/junos os evolved
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 18, 2026
  • Affected products added · juniper/junos, juniper/junos os evolved
    Oct 18, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 18, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 18, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 18, 2026 · Alertas do Telegram
  • 2025
  • CVE published
    Oct 9, 2025 · juniper

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 18, 2026 – Oct 18, 2026
  • 1× Official description updated · Oct 18, 2026 – Oct 18, 2026

References

3 on the record

Elsewhere on this site

Juniper Networks
every CVE for this vendor
Logic error
same class
CWE-754
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-101982 Junos OS and Junos OS Evolved: A EVPN peer causes an rpd crash or root-level compromise when EVPN-VPWS is used 4d
  • CVE-2026-101983 Junos OS and Junos OS Evolved: An attacker causes remote code execution when J-Web virtual-domain is configured 4d
  • CVE-2026-102077 Junos OS: MX Series with SPC3: In a source NAT scenario malformed packets will lead to resource leaks and eventually traffic stops 4d
  • CVE-2026-101979 Junos OS and Junos OS Evolved: A network attacker causes root-level code execution or denial of service when SNMP and AAA are enabled 4d
  • CVE-2026-101976 Junos OS and Junos OS Evolved: In a non-4byte-AS scenario a specific BGP update causes an rpd crash 4d
  • CVE-2026-101981 Junos OS and Junos OS Evolved: An adjacent LDP peer causes routing-engine compromise when LDP is enabled 4d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-60004 is "Junos OS and Junos OS Evolved: Specific BGP EVPN update message causes rpd crash", rated High. It affects Junos (Juniper Networks); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.42% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.