Security Advisories
Arista Networks is committed to maintaining the highest standards of security across our product portfolio. Leveraging extensive testing and monitoring of vulnerabilities to isolate and neutralize threats early, Arista's Product Security Incident Response Team (PSIRT) provides global coverage for public reporting of possible security vulnerabilities across the product portfolio.
The PSIRT team monitors industry-wide vulnerability reporting as well as providing a single point of contact for customers and interested third parties to investigate and identify potential threats. The PSIRT team also works to communicate these issues back to the user community in a timely manner.
Arista's approach to vulnerability management and links to best practice guidelines can be found here.
For technical assistance with workarounds and hotfix installations recommended in security advisories, please contact the Arista Support team at 이 이메일 주소가 스팸봇으로부터 보호됩니다. 확인하려면 자바스크립트 활성화가 필요합니다..
Report security vulnerabilities found in Arista products to the PSIRT team via 이 이메일 주소가 스팸봇으로부터 보호됩니다. 확인하려면 자바스크립트 활성화가 필요합니다.. It is recommended to use Arista's PGP key for secure and private communication directly with the PSIRT team.
Arista PSIRT is happy to work with researchers on discovered vulnerabilities in Arista products, the assignment of CVEs, and timelines for responsible disclosure. If a researcher discovers a new vulnerability they will be acknowledged in the advisory related to the vulnerability. Arista PSIRT is interested in receiving reports on issues affecting features in both Arista code as well as Open Source Software used in Arista products. Security issues found in Open Source Software which do not affect Arista products are out of the scope of Arista and should be referred to the appropriate CNA found here.
PSIRT Advisories
The following advisories and referenced materials are provided on an "as is" basis for use at your own risk. Arista Networks reserves the right to change or update the advisories without notice at any time.
Security Advisory 0182
September 9, 2026
The VeloCloud Edge software update workflow may accept update bundles without properly validating their signatures because the workflow does not restrict the digest algorithm used for artifact verification. An attacker with either sufficient privileges to upload packages to VeloCloud Orchestrator or credentials permitting direct access to an Edge may be able to install unauthorized software.
Security Advisory 0181
September 9, 2026
Insufficient validation of inputs supplied through affected VeloCloud Edge management and configuration workflows may allow an authorized management request or configuration value to be interpreted as an operating-system command. Successful exploitation may allow command execution with elevated privileges on the affected VeloCloud Edge.
Security Advisory 0180
September 9, 2026
The VeloCloud Edge and Gateway exhibit an out-of-bounds write vulnerability when processing tunneled IP fragments between authenticated overlay neighbors. This vulnerability impacts the VeloCloud VCMP tunnel protocol only.
Security Advisory 0179
September 9, 2026
On a VeloCloud Edge, an unauthenticated actor with network access to the private HA (High Availability) interconnect may trigger sensitive HA peer functions without verification.
Security Advisory 0178
September 9, 2026
SNMPv3 credentials may appear in clear text in logs or running config, enabling unauthorized SNMP access.
Security Advisory 0177
September 9, 2026
Malformed packets can cause the S4Sync agent to crash, leading to DoS for MLAG synchronization.
Security Advisory 0176
September 9, 2026
Misconfigured uRPF allows spoofed-source traffic to bypass the check and traverse the device.
Security Advisory 0175
September 9, 2026
A specially crafted packet can cause the premature expiry of multicast forwarding state on affected interfaces.
Security Advisory 0174
September 9, 2026
Unauthenticated attacker can send crafted requests to execute arbitrary code, leading to full device compromise.
Security Advisory 0173
September 9, 2026
Crafted packets can cause the OSPFv3 agent to restart, causing DoS for IPv6 routing.
