Summary
CVE-2026-93952 is a critical improper input validation flaw (CWE-20) in Arista’s VeloCloud Orchestrator (VCO) on-premises software that allows a remote, unauthenticated attacker to access privileged internal functionality on the VCO host. The flaw carries a maximum CVSSv3.1 score of 10.0 and is confirmed by Arista to be actively exploited in the wild. Successful exploitation can compromise the confidentiality, integrity, and availability of the orchestrator and of all SD-WAN edge devices and data it manages.
Technical details
- Root cause: Improper input validation (CWE-20) in the VCO web interface’s handling of requests, allowing an attacker to reach privileged internal functionality without holding tenant or operator credentials.
- Trigger conditions: The attacker needs network access to the VCO web interface, the environment must be using certificate-based authentication between VeloCloud Edge devices and the Orchestrator, and the attacker must obtain the public portion of a VeloCloud Edge authentication certificate.
- Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
- Impact: Full compromise of confidentiality, integrity, and availability of the VCO orchestrator and the data/devices it manages, including the potential deployment of malicious files and backdoor daemons on the VCO host.
- Exploitation status: Arista states this issue was discovered externally and is known to be actively exploited; observed indicators include suspicious files placed on compromised hosts and anomalous outbound network connections from VCO systems.
Affected software
- Arista VeloCloud Orchestrator (VCO) On-Prem only:
- 5.2.0 through 5.2.3.15
- 6.1.0 through 6.1.3.7
- 6.4.0 through 6.4.2.7
- 7.0.0 through 7.0.0.2
- VeloCloud Orchestrator Hosted and Dedicated (cloud-hosted) deployments were already patched by Arista prior to disclosure and are not affected.
- Arista EOS-based switches, CloudVision, and other Arista product lines are not affected.
Severity
- CVSS v3.1 Base Score: 10.0 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - (Arista also lists a CVSS v4.0 score of 9.5:
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H)
Mitigation and recommended actions
- Immediate: Upgrade VCO On-Prem to a fixed release:
- 5.2.3.16 or later (5.2.3 train)
- 6.4.2.8 or later (6.4.2 train)
- Arista has indicated additional fixes for other affected release trains (6.1.x, 7.0.x) are forthcoming — apply them as soon as they are released.
- If patching is not immediately possible:
- Restrict access to the VCO web interface to trusted, administrative-only network segments.
- Monitor VCO web access logs for suspicious URL patterns, encoded characters, or references to local services.
- Monitor for the indicators Arista has published, including the file paths
/usr/local/sbin/.vcnode.jsand/usr/local/sbin/vc-sysmond, the HTTP headerx-vc-optin nginx logs, and connections to/from the IP addresses 142.93.149.77 and 104.248.126.159. - Block unnecessary outbound network access from the VCO host and monitor for unexpected outbound HTTP/HTTPS connections.
- Audit administrator activity, credentials, and managed device states for unauthorized changes; given the potential for host compromise, consider restoring VCO from a known-trusted source after remediation.

