CVE-2026-73450

Security Advisory 0161

Published Sep 16, 2026 CVSS 4.0 · 7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

On Arista EOS platforms that have MLAG Dual Primary Detection enabled, a transmitter may send specially crafted packets that corrupt the dual‑primary state. A unauthenticated attacker who can reach the dual-primary detection segment can cause the secondary MLAG controller to incorrectly assume a dual‑primary condition, resulting in its interfaces being err‑disabled. This leads to a denial of connectivity for the affected networks while the primary switch continues to operate. The flaw exposes only availability, not confidentiality or integrity, and scopes to systems with MLAG Dual Primary Detection configured.

Affected Systems

The vulnerability affects Arista Networks EOS devices with MLAG Dual Primary Detection. Specific firmware or patch levels are not enumerated in the advisory, so all EOS releases that support this feature are potentially vulnerable. No explicit version range is supplied.

Risk and Exploitability

The CVSS score of 7.0 classifies the issue as high severity. The EPSS score is below 1 %, indicating a very low likelihood of exploitation at present, and it is not listed in CISA’s KEV catalog. Nonetheless, an attacker with local network access to the dual‑primary detection segment can craft and send packets without authentication to trigger the err‑disable logic. The risk is that a device outage can occur once the primary switch fails, as the secondary fails to recover. The attack vector is network‑based local access, requiring no credentials and minimal skill beyond packet crafting.

Remediation

Vendor Solution

The recommended resolution is to upgrade to a remediated software version at your earliest convenience.


Vendor Workaround

Restrict access to the MLAG heartbeat interface by configuring Access Control Lists (ACLs) to permit traffic strictly from the designated peer address. Insert 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. permit udp host <heartbeatPeerAddress> any eq mlag permit udp any any eq mlag ttl eq 255 deny udp any any eq mlag log Ensure administrative access for required services (e.g., SSH, NTP, SNMP) remains permitted. For instance, if the heartbeat address is reachable via the management VRF. First, construct the ingress ACL to restrict access on the MLAG heartbeat interface. switch(config)#ip access-list MLAG-HEARTBEAT-PROTECT switch(config-acl-MLAG-HEARTBEAT-PROTECT)#5 permit udp host 172.30.118.190 any eq mlag switch(config-acl-MLAG-HEARTBEAT-PROTECT)#6 permit udp any any eq mlag ttl eq 255 switch(config-acl-MLAG-HEARTBEAT-PROTECT)#7 deny udp any any eq mlag log ... Apply the ACL to management VRF: switch(config)#system control-plane switch(config-system-cp)#ip access-group MLAG-HEARTBEAT-PROTECT vrf management in switch(config-system-cp)#exit Show command to confirm the rules: switch(config)#show ip access-lists MLAG-HEARTBEAT-PROTECT Phone ACL bypass: disabled IP Access List MLAG-HEARTBEAT-PROTECT         5 permit udp host 172.30.118.190 any eq mlag         6 permit udp any any eq mlag ttl eq 255         7 deny udp any any eq mlag log         …         Total rules configured: …         Configured on Ingress: control-plane(management VRF)         Active on     Ingress: control-plane(management VRF)


OpenCVE Recommended Actions

  • Upgrade to a remediated EOS release as soon as it becomes available.
  • If upgrading is not immediately possible, enforce the ACL rules provided to block all MLAG heartbeat traffic except from the designated peer address and allow wildcard traffic with ttl 255 to reduce false positives.
  • Apply the following ACL configuration to the control‑plane of the relevant VRF and verify that ordinary administrative services (SSH, NTP, SNMP, etc.) remain reachable.

Generated by OpenCVE AI on September 18, 2026 at 12:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Arista
Arista eos
Vendors & Products Arista
Arista eos
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Security Advisory 0161
Weaknesses CWE-345
References
Metrics cvssV3_1

{'score': 6.9, 'vector': 'CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:H'}

cvssV4_0

{'score': 7, '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'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
Arista
Published
Updated
Sep 17, 2026, 5:41 PM
Reserved
Aug 12, 2026, 4:42 PM
Status
Awaiting Analysis
Published
Sep 16, 2026, 3:16 AM
Modified
Sep 17, 2026, 6:17 PM