{
  "id": "CVE-2026-73450",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-73450",
  "published_at": "2026-09-16T02:32:45.999Z",
  "title": "Security Advisory 0161",
  "vendor": "Arista Networks",
  "product": "EOS",
  "cvss": {
    "score": 7,
    "source": "cna",
    "vector": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "On affected platforms running Arista EOS with MLAG Dual Primary Detection configured, an unauthenticated attacker with access to the Dual Primary Detection network segment can send specially crafted packets to interfere with the dual-primary state. If the MLAG primary switch fails while these packets are present, the secondary switch incorrectly concludes it is in a dual-primary condition and err-disables its interfaces, leading to a traffic interruption.",
  "cwe": "CWE-345",
  "cvss_by_source": {
    "cna": 7
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Arista Networks",
        "product": "EOS",
        "ranges": [
          "\u003e= 4.36.0, \u003c= 4.36.1F",
          "\u003e= 4.35.0, \u003c= 4.35.5M",
          "\u003e= 4.34.0, \u003c= 4.34.7.1M",
          "\u003e= 4.33.0, \u003c= 4.33.9M",
          "\u003e= 0.0.0, \u003c 4.33.0"
        ],
        "fixed_in": [
          "4.33.0"
        ]
      }
    ],
    "solutions": [
      "The recommended resolution is to upgrade to a remediated software version at your earliest convenience."
    ],
    "upgrade": [
      "Upgrade EOS to 4.33.0 or later."
    ],
    "workarounds": [
      "Restrict access to the MLAG heartbeat interface by configuring Access Control Lists (ACLs) to permit traffic strictly from the designated peer address.\n\n\n\nInsert the following ACL rules into the top of the ingress ACL on the VRF where the heartbeat address is configured, while denying traffic from all other source addresses.\n\n\n\npermit udp host \u003cheartbeatPeerAddress\u003e any eq mlag\npermit udp any any eq mlag ttl eq 255\ndeny udp any any eq mlag log\n\n\n\nEnsure administrative access for required services (e.g., SSH, NTP, SNMP) remains permitted.\n\n\n\nFor instance, if the heartbeat address is reachable via the management VRF. First, construct the ingress ACL to restrict access on the MLAG heartbeat interface.\n\n\n\nswitch(config)#ip access-list MLAG-HEARTBEAT-PROTECT\nswitch(config-acl-MLAG-HEARTBEAT-PROTECT)#5 permit udp host 172.30.118.190 any eq mlag\nswitch(config-acl-MLAG-HEARTBEAT-PROTECT)#6 permit udp any any eq mlag ttl eq 255\nswitch(config-acl-MLAG-HEARTBEAT-PROTECT)#7 deny udp any any eq mlag log\n...\n\n\n\nApply the ACL to management VRF:\n\n\n\nswitch(config)#system control-plane\nswitch(config-system-cp)#ip access-group MLAG-HEARTBEAT-PROTECT vrf management in\nswitch(config-system-cp)#exit\n\n\n\nShow command to confirm the rules:\n\n\n\nswitch(config)#show ip access-lists MLAG-HEARTBEAT-PROTECT\nPhone ACL bypass: disabled\nIP Access List MLAG-HEARTBEAT-PROTECT\n        5 permit udp host 172.30.118.190 any eq mlag\n        6 permit udp any any eq mlag ttl eq 255\n        7 deny udp any any eq mlag log\n        …\n \n        Total rules configured: …\n        Configured on Ingress: control-plane(management VRF)\n        Active on     Ingress: control-plane(management VRF)"
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://www.arista.com/en/support/advisories-notices/security-advisory/24717-security-advisory-0161"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
