PoC Monitor
← All CVEs
CVE-2026-121367published 10 Nov 2026 20:10 UTCData: JSON · API

Arista Networks EOS

Security Advisory 0220

On affected Arista EOS platforms with Routing Information Protocol version 2 (RIPv2) configured, under certain conditions, RIPv2 might be silently enabled on management interfaces even when the RIP agent intends to disable it. It allows an unauthenticated attacker with access to the adjacent network to send crafted RIPv2 route advertisements to the device's management IP address. The device could accept and install those routes without authentication. Successful exploitation could allow the attacker to redirect traffic flows to an attacker-controlled destination, install more-specific routes that blackhole legitimate traffic, or otherwise disrupt network reachability for systems whose traffic passes through the affected device.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.6critical · scored by CNA · CWE-440
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Arista Networks EOS
  • >= 1.0.0, < 4.33.0F
  • >= 4.33.0F, <= 4.33.10M
  • >= 4.34.0F, <= 4.34.8M
  • >= 4.35.0F, <= 4.35.6M
  • >= 4.36.0F, <= 4.36.2F
  • 4.37.0F

Fixed in 4.33.0F

Mitigation

Upgrade EOS to 4.33.0F or later.

Workaround

switch# configure terminal switch(config)# router rip switch(config-router-rip)# shutdown switch(config-router-rip)# end (Workaround: In environments where RIP is not required, disable it within each affected VRF instance. If RIP is necessary on data interfaces but not the management subnet, verify no RIP network prefix matches the management subnet.)

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published10 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.