# CVE-2026-121289: Security Advisory 0208


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-rrpp-332g-xvjw

## What is CVE-2026-121289?

CVE-2026-121289 is a critical vulnerability in Arista Networks EOS, published on 10 Nov 2026. 

### Official description

On affected platforms running Arista EOS with BGP configured, a specially crafted packet can cause the BGP agent to crash.

Successful exploitation causes the BGP agent process to terminate, resulting in the loss of all BGP sessions on the affected device and possible disruption to network routing until the process recovers. Due to the nature of the vulnerability, it may also be possible for a sophisticated attacker to achieve arbitrary code execution, which could compromise the confidentiality and integrity of the affected system.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-121289 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121289 is a critical vulnerability in Arista Networks EOS, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121289 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-121289/ (Markdown: https://insights.sbomify.com/CVE-2026-121289/index.md)
```

## Sources

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

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