On affected platforms running Arista EOS with IPsec configured, a specially crafted packet can cause the dataplane to stop processing all IPsec traffic. The control plane may detect this condition, and attempt to reset the IPsec processing pipeline. After reset traffic may not resume being processed. There is no impact to non-IPsec traffic or to IPsec traffic not originating or terminating on the system. This issue was reported by an Arista customer.

Project Subscriptions

Vendors Products
Advisories

No advisories yet.

Fixes

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. For more information about upgrading see  https://www.arista.com/en/support/toi/tcam-profile?pn=ipsec-egress-padding-removal . This may momentarily impact traffic. Apply the configuration found at the url to create a TCAM profile and then apply the TCAM profile as shown below. switch(config)#hardware tcam switch(config-tcam)#system profile ipsec-egress-padding-removal ! WARNING! Changing TCAM profile will cause forwarding agent(s) to exit and restart. All traffic through the forwarding chip managed by the restarting forwarding agent will be dropped. Proceed [y/n]y switch(config-tcam)#   To ensure the TCAM profile has been applied, run the following command and verify the Configuration and Status values match ipsec-egress-padding-removal: switch(config-tcam)#show hardware tcam profile                      Configuration            Status FixedSystem          ipsec-egress-padding-removal ipsec-egress-padding-removal   ‘ipsec-egress-padding-removal’ differs from the ‘ipsec’ TCAM profile in two ways: * Egress IP ACLs are disabled * Fixes for BUG603398 and BUG1246592 are applied


Workaround

There are no mitigations for this vulnerability.

History

Fri, 05 Jun 2026 10:45:00 +0000

Type Values Removed Values Added
First Time appeared Arista
Arista eos
Vendors & Products Arista
Arista eos

Thu, 04 Jun 2026 23:15:00 +0000

Type Values Removed Values Added
Description On affected platforms running Arista EOS with IPsec configured, a specially crafted packet can cause the dataplane to stop processing all IPsec traffic. The control plane may detect this condition, and attempt to reset the IPsec processing pipeline. After reset traffic may not resume being processed. There is no impact to non-IPsec traffic or to IPsec traffic not originating or terminating on the system. This issue was reported by an Arista customer.
Title Arista EOS Dataplane Denial of Service via Malformed IPsec Packet
Weaknesses CWE-1286
References
Metrics cvssV3_1

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

cvssV4_0

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


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Arista

Published:

Updated: 2026-06-04T23:04:56.535Z

Reserved: 2025-08-11T18:28:43.460Z

Link: CVE-2025-8873

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-06-04T23:16:48.413

Modified: 2026-06-04T23:16:48.413

Link: CVE-2025-8873

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-05T10:07:13Z

Weaknesses