# CVE-2026-102000: Junos OS and Junos OS Evolved: An attacker causes rpd to crash when LDP is enabled

> An adjacent attacker can crash the routing process via LDP traffic, causing denial of service on Juniper devices with LDP enabled.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-wqwh-q5hg-m2rc

## What is CVE-2026-102000?

CVE-2026-102000 is a high-severity denial of service vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Reachable Assertion vulnerability in the rpd process of Juniper Networks Junos OS and Junos EVO allows an adjacent unauthenticated attacker to cause a denial of service via LDP control traffic.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2026-102000?


## How do I fix CVE-2026-102000?

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

## Is CVE-2026-102000 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102000 and fix it if it is affected.

What it is: CVE-2026-102000 is a high-severity denial of service vulnerability in Juniper Networks Junos OS, published on 14 Oct 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-2026-102000 in the wild and no public exploit code.

Affected product: Juniper Networks Junos OS. 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-2026-102000/ (Markdown: https://insights.sbomify.com/CVE-2026-102000/index.md)
```

## Sources

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

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