CVE-2025-59962 — Junos OS and Junos OS Evolved: With BGP sharding enabled, change in indirect next-hop can cause RPD crash
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (medium)+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.
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.
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.
- Identify exposed assets running the affected vendor/product/version combinations (Juniper Networks Junos, Juniper Networks Junos OS, Juniper Networks Junos Os Evolved).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Juniper Networks | Junos |
version 22.3-r3version 22.2-r1-s2version 22.2-r2version 22.2-r2-s1version 22.2-r2-s2version 22.2-r3version 22.2-r3-s1version 22.2-r3-s2 and 50 moreversion 22.3version 22.3-r1version 22.3-r1-s1version 22.3-r1-s2version 22.3-r2version 22.3-r2-s1version 22.3-r2-s2version 21.4version 22.3-r3-s1version 22.3-r3-s2version 22.4version 22.4-r1version 22.4-r1-s1version 22.4-r1-s2version 22.4-r2version 22.4-r2-s1version 22.4-r2-s2version 23.2version 23.2-r1version 23.2-r1-s1version 23.2-r1-s2version 22.2-r1version 22.2-r1-s1< 21.4version 21.4-r1version 21.4-r1-s1version 21.4-r1-s2version 21.4-r2version 21.4-r2-s1version 21.4-r2-s2version 21.4-r3version 21.4-r3-s1version 21.4-r3-s2version 21.4-r3-s3version 21.4-r3-s4version 21.4-r3-s5version 22.1-r1version 22.2version 22.1-r3-s5version 22.1-r3-s4version 22.1-r3-s3version 22.1-r3-s2version 22.1-r3-s1version 22.1-r3version 22.1-r2-s2version 22.1-r2-s1version 22.1-r2version 22.1-r1-s2version 22.1-r1-s1version 22.1 |
Vulnerable | NIST National Vulnerability Database |
| Juniper Networks | Junos OS | ≥ 23.2 and < 23.2R2≥ 22.1 and < 22.1R3-S6≥ 22.4 and < 22.4R3≥ 22.2 and < 22.2R3-S3≥ 21.4 and < 21.4R3-S6≥ 22.3 and < 22.3R3-S3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Juniper Networks | Junos Os Evolved | ≥ 23.2 and < 23.2R2-EVO≥ 22.4 and < 22.4R3-EVO≥ 22.3 and < 22.3R3-S3-EVO | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Juniper Networks | Junos Os Evolved |
version 23.2-r1-s2version 23.2-r1-s1version 23.2-r1version 23.2version 22.4-r2-s2version 22.4-r2-s1version 22.4-r2version 22.4-r1-s2 and 14 moreversion 22.4-r1-s1version 22.4-r1version 22.4version 22.3-r3-s2version 22.3-r3-s1version 22.3-r3version 22.3-r2-s2version 22.3-r2-s1version 22.3-r2version 22.3-r1-s2version 22.3-r1-s1version 22.3-r1version 22.3< 22.3 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.0 | CVSS 4.0 | Medium | — | — | sirt@juniper.net via NIST National Vulnerability Database |
| 6.0 | CVSS 4.0 | Medium | — | — | juniper via CVE Program (cve.org) e CISA ADP |
| 5.3 | CVSS 3.1 | Medium | 1.6 | 3.6 | sirt@juniper.net via NIST National Vulnerability Database |
| 5.3 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.3 | CVSS 3.1 | Medium | — | — | juniper via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:A/AC:H/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.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · juniper networks/junos os, juniper networks/junos os evolved
- SSVC assessment updated
- Record published
- Affected products added · juniper/junos, juniper/junos os evolved
- CVSS changed · 5.3
- Source status changed · → Analyzed
- Record created in this database
- 2025
- CVE published
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
Related CVEs (same products)
- Critical 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
- Critical CVE-2026-101983 Junos OS and Junos OS Evolved: An attacker causes remote code execution when J-Web virtual-domain is configured 4d
- High 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
- High 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
- High CVE-2026-101976 Junos OS and Junos OS Evolved: In a non-4byte-AS scenario a specific BGP update causes an rpd crash 4d
- High 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-59962 is "Junos OS and Junos OS Evolved: With BGP sharding enabled, change in indirect next-hop can cause RPD crash", rated Medium. It affects Junos (Juniper Networks); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.18% 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.