# CVE-2025-59959: Junos OS and Junos OS Evolved: Executing a specific show command leads to an rpd crash

> A local authenticated attacker can cause a denial of service by executing a specific show command that triggers a crash in the routing protocol daemon.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2026
- **Updated:** 16 Jan 2026
- **Also known as:** GHSA-r929-9699-qx4q

## What is CVE-2025-59959?

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

### Official description

An Untrusted Pointer Dereference vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a local, authenticated attacker with low privileges to cause a Denial-of-Service (DoS).

When the command 'show route < ( receive-protocol | advertising-protocol ) bgp > detail' is executed, and at least one of the routes in the intended output has specific attributes, this will cause an rpd crash and restart.
'show route ... extensive' is not affected.

This issue affects:

Junos OS: 

  *  all versions before 22.4R3-S8,
  *  23.2 versions before 23.2R2-S5,
  *  23.4 versions before 23.4R2-S5,
  *  24.2 versions before 24.2R2-S2,
  *  24.4 versions before 24.4R2;

Junos OS Evolved:

  *  all versions before 22.4R3-S8-EVO, 
  *  23.2 versions before 23.2R2-S5-EVO,
  *  23.4 versions before 23.4R2-S6-EVO,
  *  24.2 versions before 24.2R2-S2-EVO,
  *  24.4 versions before 24.4R2-EVO.

Weakness: CWE-822 (Untrusted Pointer Dereference)

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

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

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

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

## Is CVE-2025-59959 being exploited?

There is no known exploitation of CVE-2025-59959 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-59959 and fix it if it is affected.

What it is: CVE-2025-59959 is a medium-severity vulnerability in Juniper Junos, published on 15 Jan 2026. 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-59959 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-59959/ (Markdown: https://insights.sbomify.com/CVE-2025-59959/index.md)
```

## Sources

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

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