# CVE-2026-102072: Junos OS: An authenticated attacker causes a denial of service when the gRPC extension-service is enabled

> An authenticated attacker can cause a denial of service in Junos OS via compressed gRPC requests when the extension-service is enabled.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-734c-f3j9-8vw8

## What is CVE-2026-102072?

CVE-2026-102072 is a high-severity denial of service vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Improper Handling of Highly Compressed Data vulnerability in the gRPC library used by na-grpcd of Juniper Networks Junos OS allows an authenticated network-based attacker to cause a denial of service via a compressed gRPC request.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

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


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

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

## Is CVE-2026-102072 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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