# CVE-2026-73464: Security Advisory 0166

> Authenticated attackers with gNMI access can execute arbitrary code with root privileges on Arista EOS switches.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-hpwc-p8j3-f332

## What is CVE-2026-73464?

CVE-2026-73464 is a high-severity code injection vulnerability in Arista Networks EOS, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On affected platforms running Arista EOS with gRPC Network Management Interface (gNMI) enabled, a specially crafted request could allow a malicious authenticated client with gRPC Network Management Interface (gNMI) access to execute arbitrary code with root privileges on the switch.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-73464 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73464 is a high-severity code injection vulnerability in Arista Networks EOS, published on 16 Sep 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-73464 in the wild and no public exploit code.

Affected product: Arista Networks EOS. 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-73464/ (Markdown: https://insights.sbomify.com/CVE-2026-73464/index.md)
```

## Sources

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

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