Description
On affected platforms running Arista EOS with dual switch cards and with ingress Security ACLs configured on Switched Virtual Interfaces (SVI) in shared mode, restarting of the secondary switchcard forwarding agent or insertion of secondary switchcard, can cause security ACLs on shared SVIs to stop functioning. This may result in incorrect packet permit/deny behavior.

This issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks.
Published: 2026-09-15
Score: 6.3 Medium
EPSS: n/a
KEV: No
Impact: Ingress Security ACLs cease to function on shared SVIs after secondary switchcard restart or insertion, causing incorrect packet permit/deny behavior
Action: Apply patch
AI Analysis

Impact

The vulnerability occurs on Arista EOS platforms that use dual switch cards with ingress Security ACLs configured on Switched Virtual Interfaces (SVIs) in shared mode. When the secondary switchcard forwarding agent is restarted or a secondary switchcard is inserted, the ACLs on shared SVIs cease to function. This results in packets being incorrectly permitted or denied, potentially allowing traffic that should be blocked to pass. The weakness is classified as CWE‑1419.

Affected Systems

All Arista EOS releases supporting dual switch cards with shared‑mode SVIs are affected if they run an older version before the remediated releases. The affected releases include any 4.36.x version prior to 4.36.1F, any 4.35.x prior to 4.35.5M, any 4.34.x prior to 4.34.7M, and any 4.33.x prior to 4.33.9M. Users should verify if their device firmware meets one of those affected versions.

Risk and Exploitability

The CVSS score is 6.3, indicating medium severity. The EPSS score is not available, and the vulnerability is not listed in CISA KEV. The CVE description notes that a restart of the secondary switchcard forwarding agent or insertion of a secondary switchcard can disable ACLs, but it does not specify how an attacker could trigger these actions or what level of privileges would be required. No malicious exploitation has been reported in customer networks. Therefore, while the impact could allow unauthorized traffic if the ACLs are disabled, the exploitability for an attacker is unknown based on the supplied information.

Generated by OpenCVE AI on September 16, 2026 at 00:53 UTC.

Remediation

Vendor Solution

The recommended resolution is to upgrade to a remediated software version at your earliest convenience. Arista recommends customers move to the latest version of each release that contains all the fixes listed below. CVE-2026-73451 has been fixed in the following releases: * 4.36.1F and later releases in the 4.36.x train. * 4.35.5M and later releases in the 4.35.x train. * 4.34.7M and later releases in the 4.34.x train. * 4.33.9M and later releases in the 4.33.x train.


Vendor Workaround

The workaround is to re-configure (remove and reapply) the ingress IPv4 and IPv6 ACLs applied to all SVIs. For every SVI check the active ACL(s) applied to it, switch(config)# interface VlanNNN switch(config-if-VlNNN)# show active   Then remove the ACL(s) and re-apply them, switch(config-if-VlNNN)# no ip access-group <acl name> in switch(config-if-VlNNN)# ip access-group <acl name> in switch(config-if-VlNNN)# no ipv6 access-group <acl name> in switch(config-if-VlNNN)# ipv6 access-group <acl name> in   Note: the security provided by the ACL configuration will not be present during the removal/reapplication of the security ACLs. For more information about Security ACLs see EOS User Manual: ACLs and Route Maps https://www.arista.com/en/um-eos/eos-acls-and-route-maps .


OpenCVE Recommended Actions

  • Upgrade the Arista EOS firmware to a remediated version – 4.36.1F or later in the 4.36.x train, or the corresponding latest release in the 4.35.x, 4.34.x, or 4.33.x train.
  • Re‑configure all ingress IPv4 and IPv6 ACLs applied to SVIs: for each SVI, remove the ACLs with "no ip access-group ... in" and "no ipv6 access-group ... in", then re‑apply them with the same ACL names.
  • Initially avoid restarting the secondary switchcard or inserting a new card until the ACLs have been re‑applied; monitor switch logs for ACL disablement messages.

Generated by OpenCVE AI on September 16, 2026 at 00:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 15 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Tue, 15 Sep 2026 18:30:00 +0000

Type Values Removed Values Added
Description On affected platforms running Arista EOS with dual switch cards and with ingress Security ACLs configured on Switched Virtual Interfaces (SVI) in shared mode, restarting of the secondary switchcard forwarding agent or insertion of secondary switchcard, can cause security ACLs on shared SVIs to stop functioning. This may result in incorrect packet permit/deny behavior. This issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks.
Title On affected platforms running Arista EOS with dual switch cards and with ingress Security ACLs configured on Switched Virtual Interfaces (SVI) in shared mode, restarting of the secondary switchcard forwarding agent or insertion of secondary switchcard, can
Weaknesses CWE-1419
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Arista

Published:

Updated: 2026-09-15T19:24:42.924Z

Reserved: 2026-08-12T16:42:47.921Z

Link: CVE-2026-73451

cve-icon Vulnrichment

Updated: 2026-09-15T19:24:39.313Z

cve-icon NVD

Status : Received

Published: 2026-09-15T19:17:38.960

Modified: 2026-09-15T20:17:42.610

Link: CVE-2026-73451

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-16T01:00:14Z

Weaknesses
  • CWE-1419

    Incorrect Initialization of Resource