The short version
- The flaw. CVE-2026-93952 is an improper input validation flaw in on-premises VeloCloud Orchestrator (VCO), the server that manages Edge devices in a VeloCloud SD-WAN. Arista scored it 10.0 on CVSS 3.1 and said it was discovered externally and is known to be actively exploited.
- Who is exposed. Only orchestrators configured for certificate-based authentication from Edge to VCO are affected. An attacker also needs network access to the VCO web interface and the public part of an Edge's authentication certificate; tenant or operator credentials are not required.
- The patch gap. Fixed releases were out on 22 September for the 5.2 and 6.4 trains, and Arista had already patched its hosted and dedicated VCO offerings. Releases 6.1.3.7 and earlier and 7.0.0.2 and earlier had no fix; Arista said fixes for supported trains were coming.
- Detection. Arista says no single indicator proves compromise. It lists suspicious files, a systemd service, an nginx header and two IP addresses, and asks administrators to review VCO web access, backend and system logs.
Timeline
| Date | Event |
|---|---|
| May | Arista patches CVE-2026-7473, an Extensible Operating System (EOS) zero-day that was being actively exploited. |
| July | Arista reports CVE-2026-16812 in on-premises VCO as exploited; that flaw exposed orchestrators by default, regardless of configuration. |
| 22 Sept | Arista discloses CVE-2026-93952 as actively exploited and issues fixes for the 5.2 and 6.4 trains; CISA adds the flaw to its Known Exploited Vulnerabilities catalogue. |
What the flaw allows
Arista disclosed CVE-2026-93952 on 22 September as an improper input validation flaw in on-premises VeloCloud Orchestrator. A remote attacker with no credentials and no user interaction could reach privileged internal functions of the VCO host, affecting the confidentiality, integrity and availability of the orchestrator and the data it manages. A compromised orchestrator may also give attackers a route to the Edge devices it manages.
Exposure depends on configuration. Arista says a VCO is exposed when certificate-based authentication from the VeloCloud Edge to the orchestrator is configured, and that the attacker also needs network access to the VCO web interface and the public portion of an Edge's authentication certificate. Edges can use three modes: certificate deactivated with a pre-shared key, certificate acquire and certificate required. Arista did not say which of these meets its condition.
Fixes, workarounds and indicators
Fixed releases were available on 22 September for the 5.2 and 6.4 trains, at 5.2.3.16 and 6.4.2.8. As of that date there was no fix for 6.1.3.7 and earlier or 7.0.0.2 and earlier; Arista said fixes for affected trains still supported would be added to its advisory, and customers on unsupported trains can ask its Technical Assistance Center (TAC) about upgrades. SecurityWeek places 6.4.2.8 in the 6.1.x train, while Arista's table and other reports place it in 6.4.
Until a fix is installed, Arista recommends limiting access to the VCO web interface to trusted administrative networks, monitoring for access from known malicious IP addresses and for unexpected outbound traffic from the VCO host, blocking outbound ports that are not needed, and reviewing recent administrator activity. It also says deployments that restrict access to the web interface have a lower risk of exposure.
Arista says no single indicator proves that a VCO was compromised through this flaw. It points to VCO web access logs for requests with unusual URL-like paths, encoded characters, references to internal services or high request rates. It lists the files /usr/local/sbin/.vcnode.js and /usr/local/sbin/vc-sysmond, the service /etc/systemd/system/vc-sysmon.service, the HTTP header x-vc-opt in nginx logs, and the IP addresses 142.93.149.77 and 104.248.126.159.
Context
This is the third zero-day Arista has patched in 2026 that was being exploited in attacks, after CVE-2026-7473 in EOS in May and CVE-2026-16812 in VCO in July. Unlike the September flaw, the July one exposed orchestrators by default. CISA added CVE-2026-93952 to its Known Exploited Vulnerabilities catalogue on 22 September, the day Arista disclosed it.
What is not known yet
- Who is exploiting the flaw, and whether the activity is targeted at specific organisations or broad scanning.
- When the attacks began and how many orchestrators have been compromised.
- Which of the three Edge authentication modes Arista considers to meet its certificate-based exposure condition.
- Whether any compromised orchestrator led to data being taken or to managed Edge devices being reached.
- Whether fixes for the 6.1 and 7.0 trains have since been released.
What to do
If you run on-premises VCO
- Check which release train and version each orchestrator runs, including hosts that already carry the July fix.
- Upgrade to 5.2.3.16 or later on the 5.2 train, or 6.4.2.8 or later on the 6.4 train; consult Arista's advisory for other trains.
- If you are on 6.1.3.7 or earlier, or 7.0.0.2 or earlier, contact Arista TAC about upgrade options and restrict access in the meantime.
If you cannot patch immediately
- Limit access to the VCO web interface to trusted administrative networks.
- Block outbound ports that normal operation does not require, and monitor the VCO host for unexpected outbound traffic.
- Search for the files /usr/local/sbin/.vcnode.js and /usr/local/sbin/vc-sysmond, the vc-sysmon.service unit, the x-vc-opt nginx header and the two IP addresses Arista lists, and treat any match as suspicious.
- Review recent administrator activity and VCO web access logs for unexpected changes and anomalous requests.
If you suspect a compromise
- Preserve web access, backend application, system and database logs and file-system timestamps before remediating, where practical.
- Contact Arista TAC or your account team.
- After upgrading, rotate credentials, review administrator activity, check the state of managed Edge devices, and rebuild or restore the orchestrator from trusted sources.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.