# CVE-2025-59962: Junos OS and Junos OS Evolved: With BGP sharding enabled, change in indirect next-hop can cause RPD crash

> An attacker can cause a denial of service in Junos OS by triggering BGP route re-resolution when sharding is enabled.

- **Severity:** Medium 6.0 (`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/AU:Y/R:A/V:C/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 9 Oct 2025
- **Also known as:** GHSA-qpxp-m556-4mcr

## What is CVE-2025-59962?

CVE-2025-59962 is a medium-severity vulnerability in Juniper Junos, published on 9 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-824 (Access of Uninitialized Pointer)

## Which versions are affected by CVE-2025-59962?

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

## How do I fix CVE-2025-59962?

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

## Is CVE-2025-59962 being exploited?

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

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59962 and fix it if it is affected.

What it is: CVE-2025-59962 is a medium-severity vulnerability in Juniper Junos, published on 9 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59962 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59962/ (Markdown: https://insights.sbomify.com/CVE-2025-59962/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59962
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59962
- OSV: https://osv.dev/vulnerability/CVE-2025-59962

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59962/
Summaries are generated and may contain mistakes; the official description above is the record.