Arista Networks
Monthly
Privilege escalation through SQL injection in on-premises Arista VeloCloud Orchestrator lets any valid VCO account cross into operator-level access and impersonate the built-in superuser operator, reaching internal-only functions and potentially compromising the orchestrator host and managed data. The vendor rates the issue CVSS 9.4; hosted and Dedicated VCO deployments were affected and are reported already patched, so on-prem VCO is the remediation focus, and the supplied priority label is act_now. No public exploit identified at time of analysis, and no CISA KEV status is supplied in the provided intelligence.
Unauthenticated remote attackers can reach privileged internal functionality on customer-hosted (on-prem) Arista VeloCloud Orchestrator deployments, potentially compromising the confidentiality, integrity, and availability of the orchestrator itself and the data it manages. The vulnerable code path is exposed pre-authentication (PR:N) with no user interaction required, though the vendor's CVSS 4.0 vector and our independent assessment both assign high attack complexity (AC:H), indicating exploitation depends on specific conditions or non-trivial request crafting rather than a single trivial call. Arista-managed Hosted and Dedicated VCO instances have already been patched and are not at risk; only customer-run on-prem VCO appliances remain exposed, and no public exploit code has been identified at time of analysis.
Arbitrary code execution in Arista EOS with the gRPC Network Packet Sampling Interface (gNPSI) enabled allows an unauthenticated gNPSI client to craft a malicious request that executes code on the switch, yielding full administrative control of the device. The exploit path is gated by a hard precondition: gNPSI is not enabled by default and the gRPC endpoint must be network-reachable, which the vendor vector captures as AT:P and the advisory describes as 'under certain circumstances'; given that condition, no authentication (PR:N) or user interaction (UI:N) is needed. The vulnerability is rated critical (CVSS 4.0 base 9.2, independent 3.1 assessment AV:N/AC:H/PR:N/UI:N with high confidentiality, integrity, and availability impact), and no public exploit code has been identified at time of analysis, so realistic risk is concentrated on switches where gNPSI has been turned on and exposed to untrusted network segments.
An out-of-bounds write in Arista VeloCloud Edge and VeloCloud Gateway affects the VCMP tunnel protocol when it processes tunneled IP fragments, causing the affected process to crash and restart and briefly disrupting traffic on the affected SD-WAN node. Exploitation requires the attacker to already be an authenticated overlay neighbor with an established VCMP peer relationship to the target (assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H) - internet hosts that are unauthenticated and cannot form an overlay peer relationship cannot reach the vulnerable logic. No public exploit code has been identified at time of analysis; the impact is bounded to a temporary availability loss, with no code execution or data compromise demonstrated.
Unauthenticated elevated command execution is possible on Arista VeloCloud Edge appliances whenever High Availability is enabled, because the HA peer functions perform no caller verification (CWE-306). An attacker positioned on the private HA interconnect can invoke sensitive peer operations and obtain full confidentiality, integrity and availability impact on the Edge unit, reflected by a CVSS 4.0 base score of 8.7 (AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H). No public exploit code has been identified at time of analysis, and the exploitable surface is adjacent-only - it is the HA interconnect segment rather than the routed internet, and units without HA configured are not affected.
Premature expiry of multicast forwarding state in Arista EOS can be triggered by a specially crafted packet sent by an unauthenticated attacker who is positioned on the same Layer 2 or otherwise adjacent network segment, causing temporary loss of multicast traffic on the affected interfaces. This is an availability-only denial of service (CVSS 4.0 reports VA:H with VC:N/VI:N; the CVSS 3.1 assessment is AV:A/AC:L/PR:N/UI:N with impact limited to A:H), so the 'Information Disclosure' tag attached to the record does not reflect the actual impact. Exploitation additionally requires that multicast forwarding (PIM/IGMP) is actively configured on the targeted interface - a default, non-multicast deployment is not exposed - and the disruption is transient, since traffic resumes once forwarding state is rebuilt. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Unauthenticated remote code execution affects Arista EOS platforms on which the non-default P4Runtime service has been explicitly enabled, letting an attacker who can reach that service take complete administrative control of the switch. The defect is a code-injection flaw (CWE-94) triggered by a crafted packet during P4Runtime session initiation, rated 9.5 Critical under CVSS 4.0 and assessed as CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, with high attack complexity and a changed scope because compromise of the switching platform can extend to subsequent systems. Exposure is limited: P4Runtime is disabled by default, so stock EOS deployments are not at risk, and successful exploitation also depends on a specific timing/condition requirement (AT:P, 'Attack Requirements: Present'); Arista discovered the issue internally, reports no malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis.
Crafted OSPFv3 packets can force an unexpected restart of the OSPFv3 routing agent on Arista EOS devices that have OSPFv3 configured, causing a transient loss of routing adjacencies and traffic disruption. The flaw is an availability-only denial of service (CWE-130 improper handling of length parameters) with no code execution, data disclosure, or persistence; no authentication is required (PR:N) and no user interaction is needed (UI:N), but exploitation depends on a preconditioned packet and, per our assessment, an attacker positioned on the same OSPFv3-participating link or adjacency domain rather than arbitrarily across the internet. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor has published Security Advisory 0173.
A crafted multi-packet sequence sent by an unauthenticated attacker on the same OSPFv3 broadcast domain can force the Ospf3 agent on Arista EOS devices to restart, dropping all OSPFv3 adjacencies and potentially disrupting routing across the wider OSPF domain until the agent recovers. The flaw only affects EOS platforms where OSPFv3 is explicitly configured, and exposure is limited to link-local/L2-adjacent positions rather than routable Internet reach; exploitation is a genuine availability-only issue (CWE-617, reachable assertion), with no confidentiality or integrity impact and no public exploit identified at time of analysis, and Arista states it is not aware of malicious exploitation in customer networks.
Crafted OSPFv2 packets sent by an unauthenticated attacker on the same broadcast segment can force adjacency flapping, packet loss, and wider routing disruption on Arista EOS switches and routers that have OSPFv2 configured together with OSPFv2 authentication. Affected maintenance trains identified in EUVD are EOS below 4.33.0F and the 4.33.x (through 4.33.9M), 4.34.x (through 4.34.7M), 4.35.x (through 4.35.5M), and 4.36.x (through 4.36.1F) branches; the CVSS 4.0 base score is 7.0 (AV:A/AC:L/AT:P/PR:N/UI:N, VC:N/VI:N/VA:H/SC:N/SI:N/SA:H), and our independent 3.1 assessment scores it AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H, so the impact is strictly availability - no confidentiality or integrity loss - and the 'Information Disclosure' tag attached to this record is misleading. No CISA KEV listing is present and no public exploit code has been identified at time of analysis; authentication requirements are unauthenticated per the PR:N vector, with the compensating prerequisite being adjacency to the OSPFv2 segment rather than any credential.
Authenticated remote code execution in Arista EOS allows a malicious client with valid gRPC Network Management Interface (gNMI) access to execute arbitrary code with root privileges on the switch by sending a single specially crafted request. Only switches where gNMI has been explicitly enabled are exposed - gNMI is a non-default management API - and the attacker must already hold working gNMI credentials, which limits practical exposure to insiders or adversaries who have already compromised network-automation or management accounts, but grants them full root control of the device with low attack complexity and no user interaction. No public exploit code has been identified at time of analysis and the vulnerability is not confirmed as actively exploited (no CISA KEV listing); no EPSS score was provided. The vendor has published security advisory SA-0166 at https://www.arista.com/en/support/advisories-notices/security-advisory/24722-security-advisory-0166.
Command injection in the gRPC Network Security Interface (gNSI) Credentialz service of Arista EOS allows an authenticated, low-privileged attacker with access to the gRPC management endpoint to send a crafted request that modifies a target account's properties, potentially granting that account elevated privileges or broader access than an administrator intended (CVSS 4.0 base 8.6; assessed CVSS 3.1 8.6, AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:N). Exposure is conditional: the device must be running an affected EOS maintenance train (4.30.0F through 4.36.0.1F) with gNSI Credentialz configured, a non-default management feature, and the attacker must already hold authenticated access to that endpoint, making this a privilege-escalation-from-foothold rather than an anonymous remote compromise. A vendor patch is available per the Arista advisory; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the issue is narrower in practice than the raw score suggests because of the configuration prerequisite.
Mis-enforced authorization in Arista EOS allows an authenticated gNMI user to read or write management paths that an active gNSI Pathz policy is meant to deny, specifically when a single Pathz policy contains both a group rule and a user rule referencing the same path. Exposure is limited to EOS deployments that combine OpenConfig, a running gNMI server, and gNSI Pathz authorization - a non-default, advanced management-plane configuration - and the attacker must already hold valid gNMI credentials, consistent with the assessed vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N (confidentiality and integrity High, no availability impact). No public exploit code exists and there is no confirmed active exploitation (not in CISA KEV); the supplied CVSS 4.0 score of 7.7 overstates day-to-day risk given the narrow prerequisite stack.
Authenticated gRPC users on Arista EOS devices that have AAA-based gRPC authorization enabled for OpenConfig can have their requests evaluated at the wrong privilege level and matched against the wrong AAA method list, granting read and configuration-write access they should not hold. The flaw (CWE-266, incorrect privilege assignment) is confined to the gRPC OpenConfig path; Arista explicitly states that non-gRPC OpenConfig requests such as NETCONF are not affected, and the vulnerable configuration is not a default state. A vendor patch is available via Arista Security Advisory 0163, and no public exploit code has been identified at time of analysis; the supplied CVSS 4.0 score of 9.4 should be treated with caution, as it reflects an authorization mismatch on a management interface that requires an already-authenticated user (CVSS vector PR:H) plus a non-default AAA configuration rather than an unauthenticated, scope-changing compromise.
Command injection in Arista EOS-based products lets an authenticated user of the gRPC Network Security Interface (gNSI) Certz service escalate privileges and run arbitrary OS commands as root by sending a crafted Certz Rotate request, resulting in full device compromise; the Bootz service is affected by the same flaw. The issue is a CWE-78 OS command injection reported by Arista and carries a CVSS 4.0 base score of 9.4. There is no public exploit identified at time of analysis and the vulnerability is not listed in CISA KEV.
Improper cryptographic signature verification in the VeloCloud Edge (Arista, formerly VMware/Broadcom SD-WAN) software update workflow allows an attacker who can either upload packages to VeloCloud Orchestrator or authenticate directly to an Edge to install unauthorized software on the appliance. Because the update workflow does not constrain which digest algorithm is used to verify artifacts, a bundle signed with an unexpected or weak digest can be accepted as legitimate, resulting in arbitrary code execution with the privileges of the update process on the SD-WAN edge node. No public exploit code and no CISA KEV listing were present in the provided intelligence, although the required access level (CVSS 4.0 PR:H) means the flaw is most dangerous to insiders or anyone who has already compromised an operator account.
OS command injection in Arista VeloCloud Edge management and configuration workflows allows input supplied through those workflows to be interpreted as an operating-system command, resulting in command execution with elevated privileges on the appliance. Exploitation requires a high-privileged management request or the ability to write a configuration value, so this is primarily a privileged-insider, compromised-admin-account, or post-compromise escalation risk rather than an unauthenticated internet-facing flaw. No public exploit code or active exploitation has been identified at time of analysis, and no EPSS score was supplied with the record.
Crafted packets injected onto the MLAG Dual Primary Detection segment can trick an Arista EOS switch into falsely concluding it is in a dual-primary condition and err-disabling its interfaces, abruptly cutting off traffic for everything downstream of that switch. Exploitation needs only layer-2 adjacency to the Dual Primary Detection segment with no authentication (CVSS 4.0 AV:A/PR:N/UI:N), but it is gated by a precondition: the MLAG primary switch must fail while the crafted packets are present, so this is a conditional denial-of-service rather than a mass-exploitable remote attack. Affected EOS branches include 4.33.x, 4.34.x, 4.35.x and 4.36.x; a vendor patch is available and no public exploit code or active exploitation has been identified at time of analysis.
An authenticated SQL injection in an API component of Arista's VeloCloud Orchestrator On-Prem allows a user holding valid credentials to manipulate backend queries, exposing data beyond their intended privileges and causing the orchestrator to initiate unintended outbound network connections. Only on-prem installations on the 5.2.0, 6.1.0 and 6.4.0 branches before 5.2.3.14, 6.1.3.4 and 6.4.2.4 are affected; exploitation requires a working authenticated session (CVSS vector PR:L), so anonymous attacks are not possible, and exposure is further narrowed because the orchestrator management plane is normally reachable only from admin or management networks. EPSS is 2.83% (85th percentile) with no public exploit code and no active exploitation reported, and while the vendor's CVSS 4.0 base score is 8.5, our independent assessment treats this as a moderate-priority rather than top-priority issue given the authentication prerequisite and the on-prem-only, restricted-reachability attack surface.
Information disclosure in Arista EOS on platforms with hardware IPsec support can occur when physical interface flaps or specific agent restarts cause IPsec tunnels to re-establish while reusing existing Security Associations, leading to sequence number mismatches between endpoints. The CVSS 4.0 base score of 8.2 reflects high confidentiality impact reachable over the network, though attack requirements (AT:P) indicate specific preconditions must be met. No public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Tunnel decapsulation logic in Arista EOS fails to verify the encapsulation protocol type, allowing any tunneled packet destined for a configured decapsulation IP to be silently unwrapped and forwarded into the network. Unauthenticated remote attackers (PR:N, AV:N per CVSS 4.0) can inject traffic into network segments by exploiting this check bypass on switches with VXLAN, decap-groups, or GRE configurations. The CVE description explicitly states this issue has been reported as exploited in the wild; however, a CISA KEV entry was not confirmed in the provided data. The integrity impact is assessed as low on both the vulnerable and subsequent systems per CVSS 4.0 (VI:L/SI:L), but the network trust boundary violation in a core switching context warrants elevated operational priority.
Clear-text logging in Arista EOS with the gRPC Network Packet Sampling Interface (gNPSI) enabled can expose gNPSI client credentials to authenticated users who can read local or remote accounting logs. Affected devices are those running EOS with the non-default, opt-in gNPSI feature configured; exploitation requires an already-authenticated user with log access and specific conditions under which the credentials are written in clear text. This is a moderate-severity information-disclosure issue (vendor CVSS 4.0 score 6.0), not remote code execution or unauthenticated access, and no public exploit has been identified at time of analysis.
Cleartext disclosure of peer VRRP authentication credentials in Arista EOS log output allows an authenticated, privileged user - or anyone able to read a system receiving forwarded agent trace logs - to recover the shared secret that authenticates VRRP advertisements, without needing any presence on the VRRP network segment itself. The defect applies to EOS platforms configured with authenticated VRRP; exploitation requires high-privilege access to the switch's agent trace logs or to a downstream log collector, and the resulting impact is confidentiality-only (CVSS 4.0 base 2.1; our independent assessment rates it CVSS 3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N, i.e. PR:H and C:L). No public exploit code and no confirmed active exploitation were identified at time of analysis; this is a low-priority log-hygiene issue whose only notable edge over routine secret-in-log bugs is that the leak escapes the on-link boundary normally assumed for VRRP secrets.
Denial of service in Arista EOS affects devices that have VRRPv2 with IP Authentication Header (IP-AH) authentication explicitly configured - a non-default hardening option, so exposure is limited to networks that opted into it. An unauthenticated attacker positioned on the same layer-2 segment as the VRRP group can passively capture a legitimate authenticated VRRP advertisement and replay it indefinitely, keeping a stale master state alive and preventing a backup router from taking over the virtual gateway; hosts relying on that gateway address then lose connectivity. Impact is availability-only (no confidentiality or integrity loss, no code execution), the assessed severity is low (CVSS 3.1 5.3, AV:A/AC:L/PR:N/UI:N/A:L), and no public exploit code has been identified at time of analysis; exploitation requires layer-2 adjacency, which generally implies an insider, a compromised local host, or VLAN/physical access.
Malformed PIM Sparse Mode messages can crash the Pimsm agent on Arista EOS switches, causing a sustained denial of service when an unauthenticated, network-adjacent attacker repeatedly sends the triggering traffic. Exploitation is constrained to devices where both PIM Sparse Mode and MLAG are configured simultaneously - a non-default combination, and the attacker must be Layer-2 adjacent rather than Internet-reachable. Impact is availability-only: the Pimsm agent auto-restarts, so a single malformed message causes only a brief multicast-routing interruption, while continuous repetition is required to keep the agent in a restart loop. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (no CISA KEV listing); risk is bounded rather than urgent.
Arista EOS devices configured with SNMPv3 users store the one-way hashed, localized SNMPv3 authentication key inside the running configuration and, notably, inside sanitized configuration exports, so any authenticated user who can read either artifact obtains reusable credential material for that device's SNMP engine. With that material an attacker can issue unauthorized SNMP read operations against MIB tables or inject fraudulent trap notifications into the Network Management System, though there is no configuration-write or availability impact. The vendor discovered the flaw internally, states it is unaware of malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis; the CVSS 3.1 base score is 4.2 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N), with exploitation gated on SNMPv3 being in use and on the attacker already holding authenticated device access or a leaked sanitized configuration.
Loose-mode Unicast Reverse Path Forwarding (uRPF) on certain Arista EOS platforms can fail to drop traffic that the configured source-address verification should have rejected, so packets that ought to be filtered are still processed and forwarded by the switch or router. Only devices running Arista EOS on one of the specific (unnamed) affected platforms and explicitly configured with loose uRPF are exposed - default deployments that do not enable uRPF are not affected, and there is no confidentiality or availability impact, only a loss of filter integrity. No public exploit code and no confirmed active exploitation have been identified at time of analysis; the vendor CVSS score of 5.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N) is well calibrated to this narrow, configuration-dependent filtering failure.
A crafted OSPFv2 packet delivered by an adjacent OSPF neighbor can force an unexpected restart of the OSPF process on Arista EOS devices that run both OSPFv2 and OSPFv2 segment routing, producing an availability-only denial of service (CVSS 6.5, AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Only deployments with segment routing enabled under OSPF are exposed, since this is not a default OSPF setting, and the attacker must already be positioned on the same routing segment or link (typically a compromised or rogue device inside the OSPF domain) rather than an arbitrary internet host. No authentication or user interaction is required once adjacency is achievable, repeated packets can sustain the outage, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Incorrect authorization results in Arista EOS gNMI (gRPC Network Management Interface) can allow an already-authenticated management user to reach resources and operations slightly beyond the permissions assigned to their role. Per the assessed vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, score 4.2), exploitation requires the gNMI interface to be enabled and reachable plus a valid account with at least some gNMI access, and success depends on specific role/permission configurations - a high-complexity, low-impact condition rather than a remote unauthenticated bypass. There is no public exploit identified at time of analysis, no CISA KEV listing, and Arista states the issue was found internally with no known malicious use in customer networks.
An authenticated user with gRPC/gNSI access on Arista EOS can retain permissions that a security policy rotation was supposed to revoke, because a race condition in the gNSI Authz service causes the policy rotation to fail silently when multiple gNSI transports are configured on the device. Only non-default deployments with more than one gNSI transport are affected, Bootz is explicitly out of scope, and the flaw does not grant new privileges - it merely preserves access the attacker already legitimately held, so the outcome is a stale authorization state rather than a privilege escalation. Exploitation requires the revocation and the race to coincide, making it opportunistic rather than attacker-triggerable on demand; Arista discovered the issue internally and reports no malicious exploitation, and no public exploit code has been identified at time of analysis. The vendor's CVSS 4.0 score of 6.0 is well-calibrated for a genuinely moderate, not critical, issue.
An incorrect authorization policy can become active on Arista EOS devices through the gRPC Network Security Interface (gNSI) Authz Rotate RPC, allowing a high-privilege authenticated remote attacker to alter the device's active Authz policy. This integrity-only issue is rated CVSS 4.0 6.9 (Medium; CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N) and requires privileged gNSI management credentials; the Bootz service is explicitly unaffected. No public exploit identified at time of analysis, and Arista reports the issue was discovered internally with no known malicious use in customer networks.
Arista EOS devices that run OpenConfig-based management services (gNMI, gNSI, RESTCONF, NETCONF) can inadvertently write sensitive request and response payloads into logs that persist on the local switch or are forwarded to remote accounting/AAA servers. The leaked material includes plaintext CLI secrets such as 'username bob secret myPass' and sensitive OpenConfig YANG leafs like system/aaa/global/tacacs/config/secret-key, so the exposure is a credential/secret disclosure problem rather than an integrity or availability issue. Exploitation requires that those services be enabled, that secrets actually transit them, and that an attacker obtain read access to the resulting log or accounting sinks; triggering also requires an authenticated actor (PR:L) and some user interaction (UI:P) per the assessed vector. The issue was found internally by Arista, which states it has no evidence of malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis. gRPC-based streaming telemetry from the Streaming Telemetry Agent to CloudVision is explicitly not affected.
Affected versions of Arista EOS can write plaintext TACACS+ shared secrets into a location an operator can read, exposing the secret that protects authentication traffic between the switch and its AAA servers. Exploitation is not remote: it requires a highly privileged local session (CVSS PR:H), a non-default/specific set of circumstances (AC:H), and a user action (UI:R), which is why the score sits at 6.3 despite high confidentiality, integrity, and availability metrics. There is no public exploit code identified and the issue is not listed in CISA KEV, so this is a hardening/credential-hygiene issue rather than an actively attacked one; note that a leaked TACACS+ secret is high-value for lateral movement across network infrastructure.
Cleartext user passwords can be written into Arista EOS log files when specialized, non-standard debugging trace levels are explicitly enabled on the device. Only operators who already hold authenticated local administrative shell access and who have turned on these unusual trace levels are exposed, and a user must actually authenticate while tracing is active for credentials to be recorded. Arista discovered the flaw internally, states it is not aware of any malicious exploitation, and no public exploit code or CISA KEV entry has been identified; vendor advisory SA-0153 documents the fix
Arista EOS switches can write plaintext private keys into log files when specialized, non-standard debugging trace levels are explicitly enabled on the device. Exploitation requires an attacker to already hold authenticated local administrative access to the device shell and to have those special debug trace levels turned on, so the practical exposure is primarily insider or post-compromise rather than remote. Arista discovered the flaw internally (SA-0153), states it is unaware of malicious exploitation in customer networks, and the issue is not listed in CISA KEV and no public exploit code has been identified.
Arista EOS devices with password-based authentication enabled can accumulate orphan authentication sessions when a specially crafted password string is submitted to the management login path. Repeatedly sending such passwords exhausts the device's authentication resources, so legitimate administrators are locked out of the switch. Arista discovered the flaw internally and states it has no evidence of malicious exploitation in customer networks; no public exploit code or CISA KEV listing was identified in the supplied intelligence. The vendor-rated CVSS 4.0 score is 6.9 with availability-only impact.
Ingress Security ACLs applied to Switched Virtual Interfaces (SVIs) in shared mode on dual-switchcard Arista EOS platforms can silently stop filtering after the secondary switchcard forwarding agent restarts or a secondary switchcard is inserted, causing packets that should be denied to be permitted (and vice versa). The flaw is rated CVSS 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, CWE-1419 incorrect resource initialization) and only affects modular chassis configured with dual switch cards plus shared-mode SVI ingress ACLs. Arista discovered the issue internally and states it is not aware of any malicious exploitation in customer networks; no public exploit code or CISA KEV listing is associated with this CVE.
Server-side request forgery in Arista VeloCloud Orchestrator On-Prem lets an authenticated tenant account with at least the Enterprise Standard Admin role induce the Orchestrator to issue requests to internal services that are otherwise unreachable, because a VCO feature fails to sufficiently validate caller-supplied input. Impact is scoped to subsequent systems rather than the Orchestrator itself (low confidentiality/integrity, no availability effect), so real risk depends on what internal services a given deployment can route to. No public exploit code or active exploitation is known - Arista discovered the issue internally and confirms no malicious use in customer networks - although EPSS places it around the 82nd percentile, and vendor patches are available for the affected release trains.
Privilege escalation in Arista CloudVision Exchange (CVX) allows an authenticated attacker with network reach to the Redis service to obtain full root access across every server in the CVX cluster. The flaw stems from CVX's reliance on Redis for inter-node coordination combined with the fact that Redis traffic - including authentication - is transmitted in plaintext, meaning anyone who can sniff a single session can replay credentials to compromise the entire cluster. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Denial of service in Arista CloudVision Exchange (CVX) allows an attacker with high-privilege access to a connected switch to crash CVX agents by sending malformed TCP packets, causing instability across the CVX cluster. The flaw stems from improper input validation (CWE-20) of messages received from connected switches, and no public exploit has been identified at time of analysis.
Denial of service in Arista EOS switches and CloudVision Exchange (CVX) servers arises from improper input validation in the TCP messaging protocol that governs EOS-CVX cluster communication. Sending malformed messages in either direction - from a CVX server to an EOS switch, or vice versa - triggers a Sysdb agent crash on the EOS device (causing a soft reset) or agent crashes on the CVX server (causing cluster-wide instability). Exploitation requires the attacker to already hold high-privilege access on a device within the cluster, and no public exploit code or CISA KEV listing exists at time of analysis, making this a targeted insider or post-compromise threat rather than an opportunistic one.
On affected platforms running Arista EOS with 802.1x authentication configured on the access/trunk ports, and routing enabled on the access VLAN of the ports, a malicious supplicant may be able to. Rated high severity (CVSS 8.2), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
Affected platforms running Arista EOS with OpenConfig configured, a gNMI Set request can be run when it should have been rejected. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Affected platforms running Arista EOS with OpenConfig configured, a gNMI Set request can be run when it should have been rejected. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
On affected platforms running Arista EOS with MACsec and egress ACLs configured on the same interfaces, the ACL policies may not be enforced for packets egressing on those ports. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
In Arista’s EOS when in 802.1X mode, multi-auth unauthenticated hosts might be allowed access to a switch port if there exists an EAPOL capable device in the fallback VLAN. Rated medium severity (CVSS 6.5), this vulnerability is no authentication required, low attack complexity. No vendor patch available.
Privilege escalation through SQL injection in on-premises Arista VeloCloud Orchestrator lets any valid VCO account cross into operator-level access and impersonate the built-in superuser operator, reaching internal-only functions and potentially compromising the orchestrator host and managed data. The vendor rates the issue CVSS 9.4; hosted and Dedicated VCO deployments were affected and are reported already patched, so on-prem VCO is the remediation focus, and the supplied priority label is act_now. No public exploit identified at time of analysis, and no CISA KEV status is supplied in the provided intelligence.
Unauthenticated remote attackers can reach privileged internal functionality on customer-hosted (on-prem) Arista VeloCloud Orchestrator deployments, potentially compromising the confidentiality, integrity, and availability of the orchestrator itself and the data it manages. The vulnerable code path is exposed pre-authentication (PR:N) with no user interaction required, though the vendor's CVSS 4.0 vector and our independent assessment both assign high attack complexity (AC:H), indicating exploitation depends on specific conditions or non-trivial request crafting rather than a single trivial call. Arista-managed Hosted and Dedicated VCO instances have already been patched and are not at risk; only customer-run on-prem VCO appliances remain exposed, and no public exploit code has been identified at time of analysis.
Arbitrary code execution in Arista EOS with the gRPC Network Packet Sampling Interface (gNPSI) enabled allows an unauthenticated gNPSI client to craft a malicious request that executes code on the switch, yielding full administrative control of the device. The exploit path is gated by a hard precondition: gNPSI is not enabled by default and the gRPC endpoint must be network-reachable, which the vendor vector captures as AT:P and the advisory describes as 'under certain circumstances'; given that condition, no authentication (PR:N) or user interaction (UI:N) is needed. The vulnerability is rated critical (CVSS 4.0 base 9.2, independent 3.1 assessment AV:N/AC:H/PR:N/UI:N with high confidentiality, integrity, and availability impact), and no public exploit code has been identified at time of analysis, so realistic risk is concentrated on switches where gNPSI has been turned on and exposed to untrusted network segments.
An out-of-bounds write in Arista VeloCloud Edge and VeloCloud Gateway affects the VCMP tunnel protocol when it processes tunneled IP fragments, causing the affected process to crash and restart and briefly disrupting traffic on the affected SD-WAN node. Exploitation requires the attacker to already be an authenticated overlay neighbor with an established VCMP peer relationship to the target (assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H) - internet hosts that are unauthenticated and cannot form an overlay peer relationship cannot reach the vulnerable logic. No public exploit code has been identified at time of analysis; the impact is bounded to a temporary availability loss, with no code execution or data compromise demonstrated.
Unauthenticated elevated command execution is possible on Arista VeloCloud Edge appliances whenever High Availability is enabled, because the HA peer functions perform no caller verification (CWE-306). An attacker positioned on the private HA interconnect can invoke sensitive peer operations and obtain full confidentiality, integrity and availability impact on the Edge unit, reflected by a CVSS 4.0 base score of 8.7 (AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H). No public exploit code has been identified at time of analysis, and the exploitable surface is adjacent-only - it is the HA interconnect segment rather than the routed internet, and units without HA configured are not affected.
Premature expiry of multicast forwarding state in Arista EOS can be triggered by a specially crafted packet sent by an unauthenticated attacker who is positioned on the same Layer 2 or otherwise adjacent network segment, causing temporary loss of multicast traffic on the affected interfaces. This is an availability-only denial of service (CVSS 4.0 reports VA:H with VC:N/VI:N; the CVSS 3.1 assessment is AV:A/AC:L/PR:N/UI:N with impact limited to A:H), so the 'Information Disclosure' tag attached to the record does not reflect the actual impact. Exploitation additionally requires that multicast forwarding (PIM/IGMP) is actively configured on the targeted interface - a default, non-multicast deployment is not exposed - and the disruption is transient, since traffic resumes once forwarding state is rebuilt. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Unauthenticated remote code execution affects Arista EOS platforms on which the non-default P4Runtime service has been explicitly enabled, letting an attacker who can reach that service take complete administrative control of the switch. The defect is a code-injection flaw (CWE-94) triggered by a crafted packet during P4Runtime session initiation, rated 9.5 Critical under CVSS 4.0 and assessed as CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, with high attack complexity and a changed scope because compromise of the switching platform can extend to subsequent systems. Exposure is limited: P4Runtime is disabled by default, so stock EOS deployments are not at risk, and successful exploitation also depends on a specific timing/condition requirement (AT:P, 'Attack Requirements: Present'); Arista discovered the issue internally, reports no malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis.
Crafted OSPFv3 packets can force an unexpected restart of the OSPFv3 routing agent on Arista EOS devices that have OSPFv3 configured, causing a transient loss of routing adjacencies and traffic disruption. The flaw is an availability-only denial of service (CWE-130 improper handling of length parameters) with no code execution, data disclosure, or persistence; no authentication is required (PR:N) and no user interaction is needed (UI:N), but exploitation depends on a preconditioned packet and, per our assessment, an attacker positioned on the same OSPFv3-participating link or adjacency domain rather than arbitrarily across the internet. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor has published Security Advisory 0173.
A crafted multi-packet sequence sent by an unauthenticated attacker on the same OSPFv3 broadcast domain can force the Ospf3 agent on Arista EOS devices to restart, dropping all OSPFv3 adjacencies and potentially disrupting routing across the wider OSPF domain until the agent recovers. The flaw only affects EOS platforms where OSPFv3 is explicitly configured, and exposure is limited to link-local/L2-adjacent positions rather than routable Internet reach; exploitation is a genuine availability-only issue (CWE-617, reachable assertion), with no confidentiality or integrity impact and no public exploit identified at time of analysis, and Arista states it is not aware of malicious exploitation in customer networks.
Crafted OSPFv2 packets sent by an unauthenticated attacker on the same broadcast segment can force adjacency flapping, packet loss, and wider routing disruption on Arista EOS switches and routers that have OSPFv2 configured together with OSPFv2 authentication. Affected maintenance trains identified in EUVD are EOS below 4.33.0F and the 4.33.x (through 4.33.9M), 4.34.x (through 4.34.7M), 4.35.x (through 4.35.5M), and 4.36.x (through 4.36.1F) branches; the CVSS 4.0 base score is 7.0 (AV:A/AC:L/AT:P/PR:N/UI:N, VC:N/VI:N/VA:H/SC:N/SI:N/SA:H), and our independent 3.1 assessment scores it AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H, so the impact is strictly availability - no confidentiality or integrity loss - and the 'Information Disclosure' tag attached to this record is misleading. No CISA KEV listing is present and no public exploit code has been identified at time of analysis; authentication requirements are unauthenticated per the PR:N vector, with the compensating prerequisite being adjacency to the OSPFv2 segment rather than any credential.
Authenticated remote code execution in Arista EOS allows a malicious client with valid gRPC Network Management Interface (gNMI) access to execute arbitrary code with root privileges on the switch by sending a single specially crafted request. Only switches where gNMI has been explicitly enabled are exposed - gNMI is a non-default management API - and the attacker must already hold working gNMI credentials, which limits practical exposure to insiders or adversaries who have already compromised network-automation or management accounts, but grants them full root control of the device with low attack complexity and no user interaction. No public exploit code has been identified at time of analysis and the vulnerability is not confirmed as actively exploited (no CISA KEV listing); no EPSS score was provided. The vendor has published security advisory SA-0166 at https://www.arista.com/en/support/advisories-notices/security-advisory/24722-security-advisory-0166.
Command injection in the gRPC Network Security Interface (gNSI) Credentialz service of Arista EOS allows an authenticated, low-privileged attacker with access to the gRPC management endpoint to send a crafted request that modifies a target account's properties, potentially granting that account elevated privileges or broader access than an administrator intended (CVSS 4.0 base 8.6; assessed CVSS 3.1 8.6, AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:N). Exposure is conditional: the device must be running an affected EOS maintenance train (4.30.0F through 4.36.0.1F) with gNSI Credentialz configured, a non-default management feature, and the attacker must already hold authenticated access to that endpoint, making this a privilege-escalation-from-foothold rather than an anonymous remote compromise. A vendor patch is available per the Arista advisory; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the issue is narrower in practice than the raw score suggests because of the configuration prerequisite.
Mis-enforced authorization in Arista EOS allows an authenticated gNMI user to read or write management paths that an active gNSI Pathz policy is meant to deny, specifically when a single Pathz policy contains both a group rule and a user rule referencing the same path. Exposure is limited to EOS deployments that combine OpenConfig, a running gNMI server, and gNSI Pathz authorization - a non-default, advanced management-plane configuration - and the attacker must already hold valid gNMI credentials, consistent with the assessed vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N (confidentiality and integrity High, no availability impact). No public exploit code exists and there is no confirmed active exploitation (not in CISA KEV); the supplied CVSS 4.0 score of 7.7 overstates day-to-day risk given the narrow prerequisite stack.
Authenticated gRPC users on Arista EOS devices that have AAA-based gRPC authorization enabled for OpenConfig can have their requests evaluated at the wrong privilege level and matched against the wrong AAA method list, granting read and configuration-write access they should not hold. The flaw (CWE-266, incorrect privilege assignment) is confined to the gRPC OpenConfig path; Arista explicitly states that non-gRPC OpenConfig requests such as NETCONF are not affected, and the vulnerable configuration is not a default state. A vendor patch is available via Arista Security Advisory 0163, and no public exploit code has been identified at time of analysis; the supplied CVSS 4.0 score of 9.4 should be treated with caution, as it reflects an authorization mismatch on a management interface that requires an already-authenticated user (CVSS vector PR:H) plus a non-default AAA configuration rather than an unauthenticated, scope-changing compromise.
Command injection in Arista EOS-based products lets an authenticated user of the gRPC Network Security Interface (gNSI) Certz service escalate privileges and run arbitrary OS commands as root by sending a crafted Certz Rotate request, resulting in full device compromise; the Bootz service is affected by the same flaw. The issue is a CWE-78 OS command injection reported by Arista and carries a CVSS 4.0 base score of 9.4. There is no public exploit identified at time of analysis and the vulnerability is not listed in CISA KEV.
Improper cryptographic signature verification in the VeloCloud Edge (Arista, formerly VMware/Broadcom SD-WAN) software update workflow allows an attacker who can either upload packages to VeloCloud Orchestrator or authenticate directly to an Edge to install unauthorized software on the appliance. Because the update workflow does not constrain which digest algorithm is used to verify artifacts, a bundle signed with an unexpected or weak digest can be accepted as legitimate, resulting in arbitrary code execution with the privileges of the update process on the SD-WAN edge node. No public exploit code and no CISA KEV listing were present in the provided intelligence, although the required access level (CVSS 4.0 PR:H) means the flaw is most dangerous to insiders or anyone who has already compromised an operator account.
OS command injection in Arista VeloCloud Edge management and configuration workflows allows input supplied through those workflows to be interpreted as an operating-system command, resulting in command execution with elevated privileges on the appliance. Exploitation requires a high-privileged management request or the ability to write a configuration value, so this is primarily a privileged-insider, compromised-admin-account, or post-compromise escalation risk rather than an unauthenticated internet-facing flaw. No public exploit code or active exploitation has been identified at time of analysis, and no EPSS score was supplied with the record.
Crafted packets injected onto the MLAG Dual Primary Detection segment can trick an Arista EOS switch into falsely concluding it is in a dual-primary condition and err-disabling its interfaces, abruptly cutting off traffic for everything downstream of that switch. Exploitation needs only layer-2 adjacency to the Dual Primary Detection segment with no authentication (CVSS 4.0 AV:A/PR:N/UI:N), but it is gated by a precondition: the MLAG primary switch must fail while the crafted packets are present, so this is a conditional denial-of-service rather than a mass-exploitable remote attack. Affected EOS branches include 4.33.x, 4.34.x, 4.35.x and 4.36.x; a vendor patch is available and no public exploit code or active exploitation has been identified at time of analysis.
An authenticated SQL injection in an API component of Arista's VeloCloud Orchestrator On-Prem allows a user holding valid credentials to manipulate backend queries, exposing data beyond their intended privileges and causing the orchestrator to initiate unintended outbound network connections. Only on-prem installations on the 5.2.0, 6.1.0 and 6.4.0 branches before 5.2.3.14, 6.1.3.4 and 6.4.2.4 are affected; exploitation requires a working authenticated session (CVSS vector PR:L), so anonymous attacks are not possible, and exposure is further narrowed because the orchestrator management plane is normally reachable only from admin or management networks. EPSS is 2.83% (85th percentile) with no public exploit code and no active exploitation reported, and while the vendor's CVSS 4.0 base score is 8.5, our independent assessment treats this as a moderate-priority rather than top-priority issue given the authentication prerequisite and the on-prem-only, restricted-reachability attack surface.
Information disclosure in Arista EOS on platforms with hardware IPsec support can occur when physical interface flaps or specific agent restarts cause IPsec tunnels to re-establish while reusing existing Security Associations, leading to sequence number mismatches between endpoints. The CVSS 4.0 base score of 8.2 reflects high confidentiality impact reachable over the network, though attack requirements (AT:P) indicate specific preconditions must be met. No public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Tunnel decapsulation logic in Arista EOS fails to verify the encapsulation protocol type, allowing any tunneled packet destined for a configured decapsulation IP to be silently unwrapped and forwarded into the network. Unauthenticated remote attackers (PR:N, AV:N per CVSS 4.0) can inject traffic into network segments by exploiting this check bypass on switches with VXLAN, decap-groups, or GRE configurations. The CVE description explicitly states this issue has been reported as exploited in the wild; however, a CISA KEV entry was not confirmed in the provided data. The integrity impact is assessed as low on both the vulnerable and subsequent systems per CVSS 4.0 (VI:L/SI:L), but the network trust boundary violation in a core switching context warrants elevated operational priority.
Clear-text logging in Arista EOS with the gRPC Network Packet Sampling Interface (gNPSI) enabled can expose gNPSI client credentials to authenticated users who can read local or remote accounting logs. Affected devices are those running EOS with the non-default, opt-in gNPSI feature configured; exploitation requires an already-authenticated user with log access and specific conditions under which the credentials are written in clear text. This is a moderate-severity information-disclosure issue (vendor CVSS 4.0 score 6.0), not remote code execution or unauthenticated access, and no public exploit has been identified at time of analysis.
Cleartext disclosure of peer VRRP authentication credentials in Arista EOS log output allows an authenticated, privileged user - or anyone able to read a system receiving forwarded agent trace logs - to recover the shared secret that authenticates VRRP advertisements, without needing any presence on the VRRP network segment itself. The defect applies to EOS platforms configured with authenticated VRRP; exploitation requires high-privilege access to the switch's agent trace logs or to a downstream log collector, and the resulting impact is confidentiality-only (CVSS 4.0 base 2.1; our independent assessment rates it CVSS 3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N, i.e. PR:H and C:L). No public exploit code and no confirmed active exploitation were identified at time of analysis; this is a low-priority log-hygiene issue whose only notable edge over routine secret-in-log bugs is that the leak escapes the on-link boundary normally assumed for VRRP secrets.
Denial of service in Arista EOS affects devices that have VRRPv2 with IP Authentication Header (IP-AH) authentication explicitly configured - a non-default hardening option, so exposure is limited to networks that opted into it. An unauthenticated attacker positioned on the same layer-2 segment as the VRRP group can passively capture a legitimate authenticated VRRP advertisement and replay it indefinitely, keeping a stale master state alive and preventing a backup router from taking over the virtual gateway; hosts relying on that gateway address then lose connectivity. Impact is availability-only (no confidentiality or integrity loss, no code execution), the assessed severity is low (CVSS 3.1 5.3, AV:A/AC:L/PR:N/UI:N/A:L), and no public exploit code has been identified at time of analysis; exploitation requires layer-2 adjacency, which generally implies an insider, a compromised local host, or VLAN/physical access.
Malformed PIM Sparse Mode messages can crash the Pimsm agent on Arista EOS switches, causing a sustained denial of service when an unauthenticated, network-adjacent attacker repeatedly sends the triggering traffic. Exploitation is constrained to devices where both PIM Sparse Mode and MLAG are configured simultaneously - a non-default combination, and the attacker must be Layer-2 adjacent rather than Internet-reachable. Impact is availability-only: the Pimsm agent auto-restarts, so a single malformed message causes only a brief multicast-routing interruption, while continuous repetition is required to keep the agent in a restart loop. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (no CISA KEV listing); risk is bounded rather than urgent.
Arista EOS devices configured with SNMPv3 users store the one-way hashed, localized SNMPv3 authentication key inside the running configuration and, notably, inside sanitized configuration exports, so any authenticated user who can read either artifact obtains reusable credential material for that device's SNMP engine. With that material an attacker can issue unauthorized SNMP read operations against MIB tables or inject fraudulent trap notifications into the Network Management System, though there is no configuration-write or availability impact. The vendor discovered the flaw internally, states it is unaware of malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis; the CVSS 3.1 base score is 4.2 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N), with exploitation gated on SNMPv3 being in use and on the attacker already holding authenticated device access or a leaked sanitized configuration.
Loose-mode Unicast Reverse Path Forwarding (uRPF) on certain Arista EOS platforms can fail to drop traffic that the configured source-address verification should have rejected, so packets that ought to be filtered are still processed and forwarded by the switch or router. Only devices running Arista EOS on one of the specific (unnamed) affected platforms and explicitly configured with loose uRPF are exposed - default deployments that do not enable uRPF are not affected, and there is no confidentiality or availability impact, only a loss of filter integrity. No public exploit code and no confirmed active exploitation have been identified at time of analysis; the vendor CVSS score of 5.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N) is well calibrated to this narrow, configuration-dependent filtering failure.
A crafted OSPFv2 packet delivered by an adjacent OSPF neighbor can force an unexpected restart of the OSPF process on Arista EOS devices that run both OSPFv2 and OSPFv2 segment routing, producing an availability-only denial of service (CVSS 6.5, AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Only deployments with segment routing enabled under OSPF are exposed, since this is not a default OSPF setting, and the attacker must already be positioned on the same routing segment or link (typically a compromised or rogue device inside the OSPF domain) rather than an arbitrary internet host. No authentication or user interaction is required once adjacency is achievable, repeated packets can sustain the outage, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Incorrect authorization results in Arista EOS gNMI (gRPC Network Management Interface) can allow an already-authenticated management user to reach resources and operations slightly beyond the permissions assigned to their role. Per the assessed vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, score 4.2), exploitation requires the gNMI interface to be enabled and reachable plus a valid account with at least some gNMI access, and success depends on specific role/permission configurations - a high-complexity, low-impact condition rather than a remote unauthenticated bypass. There is no public exploit identified at time of analysis, no CISA KEV listing, and Arista states the issue was found internally with no known malicious use in customer networks.
An authenticated user with gRPC/gNSI access on Arista EOS can retain permissions that a security policy rotation was supposed to revoke, because a race condition in the gNSI Authz service causes the policy rotation to fail silently when multiple gNSI transports are configured on the device. Only non-default deployments with more than one gNSI transport are affected, Bootz is explicitly out of scope, and the flaw does not grant new privileges - it merely preserves access the attacker already legitimately held, so the outcome is a stale authorization state rather than a privilege escalation. Exploitation requires the revocation and the race to coincide, making it opportunistic rather than attacker-triggerable on demand; Arista discovered the issue internally and reports no malicious exploitation, and no public exploit code has been identified at time of analysis. The vendor's CVSS 4.0 score of 6.0 is well-calibrated for a genuinely moderate, not critical, issue.
An incorrect authorization policy can become active on Arista EOS devices through the gRPC Network Security Interface (gNSI) Authz Rotate RPC, allowing a high-privilege authenticated remote attacker to alter the device's active Authz policy. This integrity-only issue is rated CVSS 4.0 6.9 (Medium; CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N) and requires privileged gNSI management credentials; the Bootz service is explicitly unaffected. No public exploit identified at time of analysis, and Arista reports the issue was discovered internally with no known malicious use in customer networks.
Arista EOS devices that run OpenConfig-based management services (gNMI, gNSI, RESTCONF, NETCONF) can inadvertently write sensitive request and response payloads into logs that persist on the local switch or are forwarded to remote accounting/AAA servers. The leaked material includes plaintext CLI secrets such as 'username bob secret myPass' and sensitive OpenConfig YANG leafs like system/aaa/global/tacacs/config/secret-key, so the exposure is a credential/secret disclosure problem rather than an integrity or availability issue. Exploitation requires that those services be enabled, that secrets actually transit them, and that an attacker obtain read access to the resulting log or accounting sinks; triggering also requires an authenticated actor (PR:L) and some user interaction (UI:P) per the assessed vector. The issue was found internally by Arista, which states it has no evidence of malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis. gRPC-based streaming telemetry from the Streaming Telemetry Agent to CloudVision is explicitly not affected.
Affected versions of Arista EOS can write plaintext TACACS+ shared secrets into a location an operator can read, exposing the secret that protects authentication traffic between the switch and its AAA servers. Exploitation is not remote: it requires a highly privileged local session (CVSS PR:H), a non-default/specific set of circumstances (AC:H), and a user action (UI:R), which is why the score sits at 6.3 despite high confidentiality, integrity, and availability metrics. There is no public exploit code identified and the issue is not listed in CISA KEV, so this is a hardening/credential-hygiene issue rather than an actively attacked one; note that a leaked TACACS+ secret is high-value for lateral movement across network infrastructure.
Cleartext user passwords can be written into Arista EOS log files when specialized, non-standard debugging trace levels are explicitly enabled on the device. Only operators who already hold authenticated local administrative shell access and who have turned on these unusual trace levels are exposed, and a user must actually authenticate while tracing is active for credentials to be recorded. Arista discovered the flaw internally, states it is not aware of any malicious exploitation, and no public exploit code or CISA KEV entry has been identified; vendor advisory SA-0153 documents the fix
Arista EOS switches can write plaintext private keys into log files when specialized, non-standard debugging trace levels are explicitly enabled on the device. Exploitation requires an attacker to already hold authenticated local administrative access to the device shell and to have those special debug trace levels turned on, so the practical exposure is primarily insider or post-compromise rather than remote. Arista discovered the flaw internally (SA-0153), states it is unaware of malicious exploitation in customer networks, and the issue is not listed in CISA KEV and no public exploit code has been identified.
Arista EOS devices with password-based authentication enabled can accumulate orphan authentication sessions when a specially crafted password string is submitted to the management login path. Repeatedly sending such passwords exhausts the device's authentication resources, so legitimate administrators are locked out of the switch. Arista discovered the flaw internally and states it has no evidence of malicious exploitation in customer networks; no public exploit code or CISA KEV listing was identified in the supplied intelligence. The vendor-rated CVSS 4.0 score is 6.9 with availability-only impact.
Ingress Security ACLs applied to Switched Virtual Interfaces (SVIs) in shared mode on dual-switchcard Arista EOS platforms can silently stop filtering after the secondary switchcard forwarding agent restarts or a secondary switchcard is inserted, causing packets that should be denied to be permitted (and vice versa). The flaw is rated CVSS 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, CWE-1419 incorrect resource initialization) and only affects modular chassis configured with dual switch cards plus shared-mode SVI ingress ACLs. Arista discovered the issue internally and states it is not aware of any malicious exploitation in customer networks; no public exploit code or CISA KEV listing is associated with this CVE.
Server-side request forgery in Arista VeloCloud Orchestrator On-Prem lets an authenticated tenant account with at least the Enterprise Standard Admin role induce the Orchestrator to issue requests to internal services that are otherwise unreachable, because a VCO feature fails to sufficiently validate caller-supplied input. Impact is scoped to subsequent systems rather than the Orchestrator itself (low confidentiality/integrity, no availability effect), so real risk depends on what internal services a given deployment can route to. No public exploit code or active exploitation is known - Arista discovered the issue internally and confirms no malicious use in customer networks - although EPSS places it around the 82nd percentile, and vendor patches are available for the affected release trains.
Privilege escalation in Arista CloudVision Exchange (CVX) allows an authenticated attacker with network reach to the Redis service to obtain full root access across every server in the CVX cluster. The flaw stems from CVX's reliance on Redis for inter-node coordination combined with the fact that Redis traffic - including authentication - is transmitted in plaintext, meaning anyone who can sniff a single session can replay credentials to compromise the entire cluster. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Denial of service in Arista CloudVision Exchange (CVX) allows an attacker with high-privilege access to a connected switch to crash CVX agents by sending malformed TCP packets, causing instability across the CVX cluster. The flaw stems from improper input validation (CWE-20) of messages received from connected switches, and no public exploit has been identified at time of analysis.
Denial of service in Arista EOS switches and CloudVision Exchange (CVX) servers arises from improper input validation in the TCP messaging protocol that governs EOS-CVX cluster communication. Sending malformed messages in either direction - from a CVX server to an EOS switch, or vice versa - triggers a Sysdb agent crash on the EOS device (causing a soft reset) or agent crashes on the CVX server (causing cluster-wide instability). Exploitation requires the attacker to already hold high-privilege access on a device within the cluster, and no public exploit code or CISA KEV listing exists at time of analysis, making this a targeted insider or post-compromise threat rather than an opportunistic one.
On affected platforms running Arista EOS with 802.1x authentication configured on the access/trunk ports, and routing enabled on the access VLAN of the ports, a malicious supplicant may be able to. Rated high severity (CVSS 8.2), this vulnerability is remotely exploitable, no authentication required. No vendor patch available.
Affected platforms running Arista EOS with OpenConfig configured, a gNMI Set request can be run when it should have been rejected. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Affected platforms running Arista EOS with OpenConfig configured, a gNMI Set request can be run when it should have been rejected. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
On affected platforms running Arista EOS with MACsec and egress ACLs configured on the same interfaces, the ACL policies may not be enforced for packets egressing on those ports. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity.
In Arista’s EOS when in 802.1X mode, multi-auth unauthenticated hosts might be allowed access to a switch port if there exists an EAPOL capable device in the fallback VLAN. Rated medium severity (CVSS 6.5), this vulnerability is no authentication required, low attack complexity. No vendor patch available.