# CVE-2026-73460: Security Advisory 0160

> An unauthenticated attacker can cause traffic loss by injecting malformed IS-IS packets when graceful restart is enabled on Arista EOS.

- **Severity:** High 7.0 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`)
- **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:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-7q68-g5wg-74r4

## What is CVE-2026-73460?

CVE-2026-73460 is a high-severity denial of service vulnerability in Arista Networks EOS, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On affected platforms running Arista EOS with IS-IS graceful restart enabled, an unauthenticated attacker who can inject a malformed IS-IS LSP PDU packet can cause the IS-IS graceful restart procedure to terminate prematurely. This may result in traffic loss following a restart event.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-73460 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73460 is a high-severity denial of service vulnerability in Arista Networks EOS, published on 15 Sep 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-73460 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-73460/ (Markdown: https://insights.sbomify.com/CVE-2026-73460/index.md)
```

## Sources

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

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