# CVE-2026-101992: Junos OS and Junos OS Evolved: A BGP peer causes an rpd crash when automatic VPLS site ID is used

> A configured BGP peer can crash the routing daemon in Junos OS by sending a specific VPLS signaling update, causing a denial of service.

- **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`)
- **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-2qg7-r2pq-p9x6

## What is CVE-2026-101992?

CVE-2026-101992 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

An Improper Input Validation vulnerability in the routing protocol daemon (rpd) process of Juniper Networks Junos OS and Junos OS Evolved allows a configured BGP peer to cause an rpd crash via a BGP VPLS signaling update.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-101992 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101992 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-101992 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-101992/ (Markdown: https://insights.sbomify.com/CVE-2026-101992/index.md)
```

## Sources

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

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