CVE-2026-93952: Arista VeloCloud Orchestrator Zero-Day
CVE-2026-93952 in Arista VeloCloud Orchestrator (VCO) is a CVSS 10.0 input-validation vulnerability that Arista confirmed is under active exploitation as of September 22, 2026 [1]. Unlike July's default-exposed flaw, CVE-2026-93952 only affects on-premises VeloCloud Orchestrator deployments configured to authenticate Edge appliances with certificates—and two of the four affected release trains (`6.1.x` and `7.0.x`) still lack a patch [1].
Arista Networks disclosed CVE-2026-93952 on September 22, 2026, warning customers that attackers are actively exploiting on-premises VeloCloud Orchestrator (VCO) servers that manage enterprise SD-WAN fleets [1]. CVE-2026-93952 carries a maximum CVSS 3.1 base score of 10.0 and was reported to Arista externally rather than uncovered during internal quality assurance testing [1].
CVE-2026-93952 marks the second time in three months that on-premises VeloCloud Orchestrator has been hit by a CVSS 10.0 flaw under active exploitation. In July 2026, Arista patched CVE-2026-16812, a separate OS command injection vulnerability in VeloCloud Orchestrator that was also exploited in the wild [4], [5]. Because CVE-2026-93952 and CVE-2026-16812 target different code paths, teams running a structured vulnerability management plan must track and remediate both advisories independently.
The diagram below illustrates how CVE-2026-93952 threatens the central VeloCloud Orchestrator management plane that controls distributed SD-WAN Edge appliances:
What Arista Disclosed About CVE-2026-93952
CVE-2026-93952 in VeloCloud Orchestrator is described in Arista Security Advisory 0183 as a flaw that "may allow a remote attacker to access privileged internal functionality and impact the VCO host," compromising the confidentiality, integrity, and availability of the orchestrator and the SD-WAN data it manages [1]. Arista classifies the underlying root cause of CVE-2026-93952 as CWE-20 (Improper Input Validation), distinguishing it from July's OS command injection bug (CVE-2026-16812) [1], [4].
Regarding real-world attacks against CVE-2026-93952, Arista's advisory states directly: "This issue was discovered externally and is known to be actively exploited" [1]. Arista has not disclosed when exploitation of CVE-2026-93952 began, how many VeloCloud Orchestrator deployments were breached, or which threat actor is operating the campaign. The Hacker News reported reaching out to Arista for additional details on the CVE-2026-93952 attacks without receiving an immediate response [2].
Which VeloCloud Orchestrator Deployments Are Exposed to CVE-2026-93952
CVE-2026-93952 only exposes on-premises VeloCloud Orchestrator instances where certificate-based authentication from the VeloCloud Edge to the Orchestrator is configured [1]. That configuration prerequisite separates CVE-2026-93952 from July's CVE-2026-16812, which exposed every VCO installation by default with "no configuration that can prevent the exposure" [5].
To determine whether CVE-2026-93952 applies to your environment, check how your VeloCloud Edges authenticate to VeloCloud Orchestrator. According to Arista's SD-WAN 7.0 Administration Guide, VeloCloud Edges use one of three authentication modes [3]:
- Certificate Deactivated: Uses a pre-shared key (PSK) rather than client certificates [3].
- Certificate Acquire: Uses an orchestrator-issued certificate alongside fallback provisioning [3].
- Certificate Required: Enforces strict certificate authentication issued by the orchestrator [3].
Arista's advisory for CVE-2026-93952 does not distinguish between Certificate Acquire and Certificate Required—it states broadly that VCO is vulnerable whenever certificate-based Edge authentication is enabled [1], [2]. Beyond that setting, exploiting CVE-2026-93952 requires two additional conditions: the attacker must have network access to the VCO web interface and must possess the public portion of an Edge's authentication certificate [1]. No VCO operator or tenant login credentials are required to trigger CVE-2026-93952.
The diagram below maps the unauthenticated attack path for CVE-2026-93952 based on Arista's published preconditions:
CVSS 3.1 vs. CVSS 4.0 Scoring for CVE-2026-93952
Arista scored CVE-2026-93952 at 10.0 under CVSS 3.1 (`AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`) and 9.5 under 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`) [1]. Teams familiar with understanding CVSS 4.0 triage will notice why CVE-2026-93952 drops by half a point in the newer standard: Arista rated Attack Complexity as High (`AC:H`) under CVSS 4.0 while rating it Low (`AC:L`) under CVSS 3.1 [1]. Regardless of that scoring nuance, confirmed active exploitation of CVE-2026-93952 puts exposed VCO servers at immediate operational risk.
VeloCloud Orchestrator Versions Affected by CVE-2026-93952
CVE-2026-93952 spans four on-premises VeloCloud Orchestrator release trains, and as of September 22, 2026, Arista has released patches for only two of them (`5.2.x` and `6.4.x`) while leaving `6.1.x` and `7.0.x` awaiting fixes [1].
The table below details the exact VeloCloud Orchestrator release trains affected by CVE-2026-93952 and the corresponding patched builds:
| VCO Release Train | Versions Vulnerable to CVE-2026-93952 | Patched Version |
|---|---|---|
| 5.2.x | 5.2.3.15 and earlier | 5.2.3.16 and later |
| 6.1.x | 6.1.3.7 and earlier | Not yet available |
| 6.4.x | 6.4.2.7 and earlier | 6.4.2.8 and later |
| 7.0.x | 7.0.0.2 and earlier | Not yet available |
Cloud-managed VeloCloud Orchestrator Hosted and Dedicated instances—which Arista operates directly for customers—have already been patched against CVE-2026-93952 [1]. Arista also confirmed that standalone VeloCloud Gateway and VeloCloud Edge appliances are not directly affected by CVE-2026-93952, though an attacker who compromises VCO can abuse management trust to reach connected Edges [1]. Customers running end-of-support VCO trains affected by CVE-2026-93952 should contact Arista's Technical Assistance Center (TAC) for migration options [1].
Indicators of Compromise (IOCs) for CVE-2026-93952
Detecting exploitation of CVE-2026-93952 requires inspecting both web access logs and underlying Linux host artifacts on the VeloCloud Orchestrator appliance. Arista notes that no single log line guarantees a breach via CVE-2026-93952, advising administrators to hunt VCO web access logs for requests containing unusual URL-like paths, encoded characters, references to internal loopback services, or abnormal request spikes [1].
Arista published five specific Indicators of Compromise (IOCs) observed in active CVE-2026-93952 intrusions [1]:
- Rogue Node Script:
/usr/local/sbin/.vcnode.js - Malicious Binary:
/usr/local/sbin/vc-sysmond(MD5:dc78e206eaeadec59fc5801fe4556bd0) - Rogue Systemd Service:
/etc/systemd/system/vc-sysmon.service - Suspicious HTTP Header: Presence of the
x-vc-optheader inside VCO nginx logs - Attacker IP Addresses: Inbound or outbound network traffic involving
142.93.149.77or104.248.126.159
Because CVE-2026-93952 attackers plant persistence using systemd unit files (vc-sysmon.service) and hidden binaries masquerading as native VeloCloud daemons, defenders should pair log review with host integrity checks based on a Linux server hardening baseline. If any of these CVE-2026-93952 indicators appear on your orchestrator, execute your incident response plan immediately: Arista asks administrators to preserve VCO web logs, backend application logs, system logs, database logs, and filesystem timestamps before wiping or patching the host [1].
The workflow diagram below summarizes Arista's four-step containment and remediation sequence for CVE-2026-93952:
Interim Mitigations for Unpatched VCO 6.1.x and 7.0.x Trains
Organizations running VeloCloud Orchestrator `6.1.x` or `7.0.x` cannot yet patch CVE-2026-93952 and must rely on network isolation to cut off the attack vector [1]. Applying network segmentation best practices and enforcing zero trust microsegmentation around the VCO management interface prevents unauthenticated internet hosts from reaching the vulnerable endpoint.
Specifically, Arista recommends the following compensating controls to reduce CVE-2026-93952 exposure while awaiting patches [1]:
- Restrict VeloCloud Orchestrator web interface access strictly to trusted administrative networks.
- Block and alert on traffic to or from the known CVE-2026-93952 attacker IPs (`142.93.149.77` and `104.248.126.159`).
- Restrict unnecessary outbound ports from the VCO host to prevent reverse shells or secondary payload downloads.
- Monitor the VCO Linux filesystem for unauthorized systemd services, Node.js scripts, or webshells.
- After patching CVE-2026-93952, rotate all orchestrator credentials, audit recent administrator configuration changes, verify the integrity of managed SD-WAN Edge appliances, and rebuild the VCO host from known-clean media if any IOC was triggered [1].
What Remains Unknown About the CVE-2026-93952 Campaign
Key operational details surrounding CVE-2026-93952 remain undisclosed. Arista has not published the exact HTTP request structure that triggers the CWE-20 input validation bypass in CVE-2026-93952, nor has it explained how attackers obtained the public portion of target Edge authentication certificates in real-world intrusions [1]. Furthermore, neither Arista nor independent incident responders have attributed the CVE-2026-93952 exploitation activity to a named threat group or disclosed the number of compromised SD-WAN environments [2].
Immediate Priorities for VeloCloud Orchestrator Administrators
Defending VeloCloud Orchestrator against CVE-2026-93952 comes down to three immediate checks today. First, verify whether your on-premises VeloCloud Orchestrator uses certificate-based Edge authentication (`Certificate Acquire` or `Certificate Required`) [3]. Second, check your VCO build against Arista's advisory and upgrade immediately to `5.2.3.16` or `6.4.2.8` if you are on those trains, or lock down VCO web UI ingress if you are waiting on patches for `6.1.x` and `7.0.x` [1]. Third, sweep `/usr/local/sbin/`, `/etc/systemd/system/`, and nginx logs for the five CVE-2026-93952 IOCs before applying updates so you do not accidentally overwrite forensic evidence of an active compromise [1].
Leave a Comment (Authenticated Users)