# CVE-2026-33795: Junos OS and Junos OS Evolved: An attacker causes a routing-daemon crash when BGP Prefix-SID routes are re-advertised

> An unauthenticated attacker can crash the routing daemon by re-advertising BGP Prefix-SID routes, causing a denial of service on Juniper devices.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-5ggv-3g39-x5c7

## What is CVE-2026-33795?

CVE-2026-33795 is a high-severity vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Numeric Truncation Error vulnerability in the rpd process of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker to cause a denial of service via a BGP Prefix-SID route advertisement that is subsequently re-advertised.

This issue does not affect versions of Junos OS prior to 20.4R1.
This issue does not affect versions of Junos OS Evolved prior to 20.4R1-EVO

Weakness: CWE-197 (Numeric Truncation Error)

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


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

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

## Is CVE-2026-33795 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33795 is a high-severity vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33795 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-33795/ (Markdown: https://insights.sbomify.com/CVE-2026-33795/index.md)
```

## Sources

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

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