Skip to main content
Menu
CVEs

Arista EOS stack overflow in BGP agent allows crash or code execution

CVE-2026-121289Published November 10, 2026, updated

9.8CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 4.33.0F
Who is exposed
Not reported

Summary

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.

Who should check

Teams running Arista EOS with BGP configured under the multi-agent routing protocol model

“On affected platforms running Arista EOS with BGP configured”

arista.com

What to do

Upgrade to a fixed version: 4.33.0F.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-121289 (Security Advisory 0208), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121289 (entry last updated 2026-11-13):
Affected:
- Arista Networks EOS: from 4.36.0F, through 4.36.2F; from 4.35.0F, through 4.35.6M; from 4.34.0F, through 4.34.8M; from 4.33.0F, through 4.33.10M; from 4.25.1F, fixed in 4.33.0F
Fixed versions: 4.33.0F.
Conditions (all must be true for the bug to be hit):
- Arista EOS with BGP configured (source: https://www.arista.com/en/support/advisories-notices/security-advisory/25030-security-advisory-0208)
- BGP routing protocols run under the multi-agent model (source: https://www.cve.org/CVERecord?id=CVE-2026-121289)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-121289 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121289 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.arista.com/en/support/advisories-notices/security-advisory/25030-security-advisory-0208
- https://www.cve.org/CVERecord?id=CVE-2026-121289
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121289
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121289"}.

Affected versions

cve.now Index

30of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now3 days
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 10Nov 22
  • EPSS: 0.64%
  • Posted on X by cve.now Nov 10

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisoryarista.com · en/support/advisories-notices/security-advisory/25030-security-advisory-0208
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-121289
RecordNVD · CVE-2026-121289

Questions about CVE-2026-121289

Is CVE-2026-121289 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Crashing the BGP agent drops all BGP sessions on the device and can disrupt routing. The impact also includes a possible arbitrary code execution by a sophisticated attacker, which would compromise confidentiality and integrity.

Source: arista.com, cve.org

Which versions are affected by CVE-2026-121289?

EOS: from 4.36.0F through 4.36.2F; from 4.35.0F through 4.35.6M; from 4.34.0F through 4.34.8M; from 4.33.0F through 4.33.10M; from 4.25.1F before 4.33.0F.

Source: cve.now feed data

Am I affected, and how do I check?

The listed ranges are Arista EOS 4.36.0F through 4.36.2F, 4.35.0F through 4.35.6M, 4.34.0F through 4.34.8M, and 4.33.0F through 4.33.10M, plus a range starting at 4.25.1F with a fixed version of 4.33.0F. The setup is EOS with BGP configured and BGP running under the multi-agent routing model. To check, run the show version command for the EOS release and look at the service routing protocols model setting.

Source: arista.com, cve.org

How do I fix CVE-2026-121289?

The checked facts do not name a fixed version or vendor patch IDs for this advisory, so consult Security Advisory 0208 for the upgrade target before changing anything.

Source: arista.com, cve.org

No corrections so far. Something wrong on this page? Report an error.