ACL bypass via incorrect ingress policy enforcement
Published May 27, 2025 · Updated May 28, 2025
Access-control failure in Arista EOS 4.33.2F allows remote authenticated users to bypass ingress ACLs with adjacent traffic. On 7060X6 switches, EOS misapplies IPv4, MAC, or standard IPv6 ingress ACLs across multiple Ethernet interfaces or LAGs, permitting denied packets or dropping permitted packets. Exposure requires an affected ACL to be configured and active on multiple Ethernet interfaces or at least one LAG; reported impact is limited to incorrect packet filtering.
Summary
What happened
Access-control failure in Arista EOS 4.33.2F allows remote authenticated users to bypass ingress ACLs with adjacent traffic. On 7060X6 switches, EOS misapplies IPv4, MAC, or standard IPv6 ingress ACLs across multiple Ethernet interfaces or LAGs, permitting denied packets or dropping permitted packets. Exposure requires an affected ACL to be configured and active on multiple Ethernet interfaces or at least one LAG; reported impact is limited to incorrect packet filtering.
The record
- CVE
- CVE-2025-2826
- Published
- May 27, 2025
- Updated
- May 28, 2025
- Vendor
- Arista Networks
- Product
- Arista EOS
- Classifications
- CWE-1284, T1599
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2025CVE publishedPublication date reported by the CVE source.
- May 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.33.2F
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo