CVE-2025-2826: n affected platforms running Arista EOS, ACL policies may not be enforced. IPv4 ingress ACL, MAC ingress ACL, or IPv6 standard ingress ACL enabled on one or more ethernet or LAG interfaces may result in ACL policies not being enforced for ingress packets.

Published May 27, 2025

Updated

n affected platforms running Arista EOS, ACL policies may not be enforced. IPv4 ingress ACL, MAC ingress ACL, or IPv6 standard ingress ACL enabled on one or more ethernet or LAG interfaces may result in ACL policies not being enforced for ingress packets. This can cause incoming packets to incorrectly be allowed or denied. The two symptoms of this issue on the affected release and platform are:

Packets which should be permitted may be dropped and, Packets which should be dropped may be permitted.

Affected Software

1 affected component

Arista EOS

Remediation

Information

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. For more information about upgrading see EOS User Manual: Upgrades and Downgrades https://www.arista.com/en/um-eos/eos-upgrades-and-downgrades CVE-2025-2826 has been fixed in the following releases: * 4.33.2.1F, 4.33.3F and later releases in the 4.33.x train

Event History

May 27, 2025

CVE Published

via MITRE·10:22 PM

Data Sourced

via MITRE·10:22 PM

RemedyDescriptionSeverityWeakness

Data Sourced

via NVD·11:15 PM

DescriptionSeverityWeakness

Frequently Asked Questions

What is the severity of CVE-2025-2826?

CVE-2025-2826 has a high severity rating due to the potential bypass of crucial ACL policies.

How do I fix CVE-2025-2826?

To fix CVE-2025-2826, ensure that the latest security patches for Arista EOS are applied.

What platforms are affected by CVE-2025-2826?

CVE-2025-2826 affects all platforms running Arista EOS where ACL policies may not be enforced.

What are the potential impacts of CVE-2025-2826?

The potential impacts of CVE-2025-2826 include unauthorized access and traffic being allowed through interfaces without proper filtering.

Is there a workaround for CVE-2025-2826 until a patch is applied?

A temporary workaround for CVE-2025-2826 may involve manually verifying ACL configurations and monitoring ingress traffic.