Read the docs

Incorrect MD5 authentication in Arista EOS RIPv2 accepts forged routes

Priority LOW 27CWE-303Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · High · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Arista Networks EOS versions 4.37.0F, 4.36.0F through 4.36.2F, 4.35.0F through 4.35.6M, 4.34.0F through 4.34.8M, 4.33.0F through 4.33.10M, from 4.32.0F before 4.33.0F, and 1.0.0 before 4.32.0F are affected. Incorrect implementation of the MD5 authentication algorithm for RIPv2 lets the device accept unauthorized route updates (CWE-303). An unauthenticated attacker on an adjacent network segment can inject crafted RIPv2 packets when RIPv2 MD5 authentication is configured on the interface, causing the device to install routes that redirect, loop or blackhole traffic.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

An unauthenticated attacker on an adjacent network segment can bypass MD5 authentication and have unauthorized RIP route updates accepted by the device. Successful exploitation requires that RIPv2 MD5 authentication is configured on the affected interface. An attacker who can inject crafted RIPv2 packets could cause the device to install routes that redirect network traffic through attacker-controlled paths, create routing loops, or blackhole traffic, disrupting network connectivity.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00236 14th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
AristaEOS4.37.0F; 4.36.0F – 4.36.2F; 4.35.0F – 4.35.6M; 4.34.0F – 4.34.8M; 4.33.0F – 4.33.10M; 4.32.0F to before 4.33.0F; 1.0.0 to before 4.32.0F—No fix listedCNA
  • EOS VendorArista Affected 4.37.0F; 4.36.0F – 4.36.2F; 4.35.0F – 4.35.6M; 4.34.0F – 4.34.8M; 4.33.0F – 4.33.10M; 4.32.0F to before 4.33.0F; 1.0.0 to before 4.32.0F Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Arista Networks EOS.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Advisory ·

    Arista Networks EOS — arista.com/en/support/advisories-notices/security-advisory/…

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-89308 Buffer underwrite in Arista EOS RIP agent can crash routing servicePriority LOW 35

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-121288
  2. 2026-11-10 Alias added: GHSA-vm32-9w3q-25c6
  3. 2026-11-12 Priority changed: MEDIUM → LOW
  4. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2026-79524 Privilege escalation in Arista VeloCloud Orchestrator on-premises KEVCVSS 4.0CRITICAL 9.4
  • TI-2026-63212 Input validation flaw in Arista VeloCloud Orchestrator on-prem KEVCVSS 4.0CRITICAL 9.5
  • TI-2026-13992 OS command injection in VeloCloud Orchestrator On-Prem KEVCVSS 4.0CRITICAL 10.0
  • TI-2014-05975 GNU Bash environment variable parsing flaw lets attackers write files KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-05157 Code execution in GNU Bash through crafted environment variables KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-23989 Incorrect resource transfer in Linux kernel algif_aead KEVCVSS 3.1HIGH 7.8
See all 242 →

Sources