CVE-2025-59962: Junos OS and Junos OS Evolved: With BGP sharding enabled, change in indirect next-hop can cause RPD crash
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Juniper Networks Junos OS 21.4R3-S6, 22.1R3-S6, 22.2R3-S3; Juniper Networks Junos OS Evolved 22.3R3-S3-EVO, 22.4R3-EVO, 23.2R2-EVO.
Low priority for now. Upgrade to Juniper Networks Junos OS 21.4R3-S6, 22.1R3-S6, 22.2R3-S3; Juniper Networks Junos OS Evolved 22.3R3-S3-EVO, 22.4R3-EVO, 23.2R2-EVO or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 9, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-824
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · juniper
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| juniper | junos | cpe:2.3:o:juniper:junos |
| juniper | junos os evolved | cpe:2.3:o:juniper:junos_os_evolved |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (juniper). Independent of NVD's CPE analysis and usually ahead of it.
Juniper Networks Junos OS
- 21.4 and later · before 21.4R3-S6affected · semver
- 22.1 and later · before 22.1R3-S6affected · semver
- 22.2 and later · before 22.2R3-S3affected · semver
- 22.3 and later · before 22.3R3-S3affected · semver
- 22.4 and later · before 22.4R3affected · semver
- 23.2 and later · before 23.2R2affected · semver
- before 21.3R1not affected · semver
Juniper Networks Junos OS Evolved
- 22.3 and later · before 22.3R3-S3-EVOaffected · semver
- 22.4 and later · before 22.4R3-EVOaffected · semver
- 23.2 and later · before 23.2R2-EVOaffected · semver
- before 21.3R1-EVOnot affected · semver
Affected versions · NVD (11)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junosbefore 21.4
- juniper junos21.4
- juniper junos22.1
- juniper junos22.2
- juniper junos22.3
- juniper junos22.4
- juniper junos23.2
- juniper junos os evolvedbefore 22.3
- juniper junos os evolved22.3
- juniper junos os evolved22.4
- juniper junos os evolved23.2
Same product
juniper: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-36845Junos OS: EX and SRX Series: A PHP vulnerability in J-Web allows an unauthenticated to control an important environment variableKEV98Now
- CVE-2023-36846Junos OS: SRX Series: A vulnerability in J-Web allows an unauthenticated attacker to upload arbitrary filesKEV79This week
- CVE-2023-36844Junos OS: EX Series: A PHP vulnerability in J-Web allows an unauthenticated attacker to control important environment variablesKEV78This week
Published before and after this one in the same product
- ← EarlierCVE-2025-52960Oct 9, 2025 · Junos OS: SRX Series and MX Series: Receipt of specific SIP packets in a high utilization situation causes a flowd/mspmand crash32Monitor
- ← EarlierCVE-2025-59957Oct 9, 2025 · Junos OS: EX4600 Series and QFX5000 Series: An attacker with physical access can open a persistent backdoor28Monitor
- Later →CVE-2025-59964Oct 9, 2025 · Junos OS: SRX4700: When forwarding-options sampling is enabled any traffic destined to the RE will cause the forwarding line card to crash and restart34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Juniper Networks Junos OS | 21.4R3-S6 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.1R3-S6 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.2R3-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.3R3-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.4R3 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.2R2 | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.3R3-S3-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.4R3-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 23.2R2-EVO | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-824 · Access of Uninitialized PointerCVSS vector
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:A/V:C/RE:M/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.