GPU VulnDB

Database/Firmware, BMC & network fabric

Arista EOS: RIPv2 silently enabled on management interfaces accepts unauthenticated routes

CVSS 6.1CVE-2026-121367Firmware, BMC & network fabriccurated

Impact

On affected EOS releases with RIPv2 configured, RIP can end up active on management interfaces even though the RIP agent means to disable it there. Anyone who can reach the management IP from the adjacent network can send crafted RIPv2 advertisements, and the switch installs them without authentication. The attacker can then redirect traffic to a destination they control, or install more-specific routes that blackhole legitimate traffic. On a GPU cluster fabric or management network, that can cut nodes off from storage, schedulers or BMC access, or send their traffic through an attacker-controlled host.

Who can reach it

Unauthenticated attacker on the network segment adjacent to the switch's management interface. Only switches with RIPv2 configured are affected.

What to do

Upgrade EOS to a fixed release listed in Arista Security Advisory 0220. The record does not name a fixed version. An EOS upgrade usually means a switch reload, so plan for the traffic impact or use redundant fabric paths. Until then, restrict who can reach the management network, and consider filtering RIP on management interfaces or removing RIPv2 where it is not needed.

References

Related entries

All Firmware, BMC & network fabric entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.