# CVE-2026-101978: Command injection in Junos OS Evolved

> An attacker on the management LAN can execute root commands via a crafted gRPC response during zero-touch provisioning.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/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:** 16 Oct 2026
- **Also known as:** GHSA-pr89-h5hv-gj8j

## What is CVE-2026-101978?

CVE-2026-101978 is a high-severity command injection vulnerability in Juniper Networks Junos OS Evolved, 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 OS Command Injection vulnerability in the bootzd zero-touch provisioning daemon of Juniper Networks Junos OS Evolved on PTX Series allows an unauthenticated attacker on the management LAN to execute commands as root via a crafted gRPC response.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-101978 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101978 is a high-severity command injection vulnerability in Juniper Networks Junos OS Evolved, 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-101978 in the wild and no public exploit code.

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

## Sources

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

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