Security Advisory 0221
- Exploited
- No known exploitation
- Fix
- Fixed in 4.33.0F, 4.32.0F
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.33.0F, 4.32.0F.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
An unauthenticated attacker on an adjacent network segment can send crafted RIPv2 packets to a RIP-enabled interface on the device to trigger the Rip agent crash without providing valid credentials. Repeated exploitation reliably interrupts routing service on the affected device, which may also disrupt routing for other devices that depend on it. In a worst-case scenario, the vulnerability may allow an attacker to execute arbitrary code on the affected device.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.33.0F, 4.32.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-121287 (Security Advisory 0221), 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-121287 (entry last updated 2026-11-10): 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.32.0F, fixed in 4.33.0F; from 1.0.0, fixed in 4.32.0F Fixed versions: 4.33.0F, 4.32.0F. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-121287 is not listed as of cve.now's last read. This KEV status is for CVE-2026-121287 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/25043-security-advisory-0221 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-121287 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-121287.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- 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.32.0F · fixed in 4.33.0F; From 1.0.0 · fixed in 4.32.0F
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121287
Is CVE-2026-121287 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
Which versions are affected by CVE-2026-121287?
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.32.0F before 4.33.0F; from 1.0.0 before 4.32.0F.Source: cve.now feed data
How do I fix CVE-2026-121287?
Upgrade to a fixed version: 4.33.0F, 4.32.0F.Source: cve.now feed data