Security researchers are warning that a critical command injection vulnerability in on-premises deployments of Arista’s VeloCloud Orchestrator (VCO) is being actively exploited, giving remote attackers a path to privileged internal functions and, potentially, full control of the orchestrator host.

A Perfect 10

The flaw, tracked as CVE-2026-16812, has been assigned the maximum possible severity score of 10.0 under both CVSS v3.1 and CVSS v4.0. It falls under CWE-78, the weakness class covering improper neutralization of operating system commands, meaning specially crafted input can be interpreted and executed as a system command by the underlying host.

VeloCloud Orchestrator is the management plane for SD-WAN environments, overseeing connected VeloCloud Edge devices, network configurations, digital certificates, and other operationally sensitive data. A successful attack threatens the confidentiality, integrity, and availability of both the orchestrator itself and everything it manages.

No Credentials Required

According to Arista’s advisory, the vulnerable function was originally designed for internal use only, but in affected on-premises installations it is reachable remotely. Critically, attackers don’t need any VCO tenant or operator credentials to exploit it, they only need network access to the VCO web interface, which is exposed by default in most deployments.

The affected version ranges are:

• VCO 5.2.x before 5.2.3.14
• VCO 6.1.x before 6.1.3.4
• VCO 6.4.x before 6.4.2.4
• VCO 7.0.x before 7.0.0.1

Arista’s hosted and dedicated VCO services were already patched before the advisory went public, so the exposure is limited to organizations running on-premises orchestrator instances. VeloCloud Gateway, VeloCloud Edge, other hosted VCO offerings, and the broader family of Arista EOS-based products are not affected by this issue. End-of-support release trains have not been assessed and should be treated with extra caution.

Signs of Compromise to Watch For

Arista says there is no single definitive indicator that confirms exploitation, but administrators should scrutinize web requests containing unusual URL path components, encoded characters, references to local services, or abnormally high request volumes. Reviewing backend application logs, operating system logs, database logs, and file-system timestamps for unexplained changes is also recommended.

The advisory names three IP addresses already observed attacking vulnerable orchestrators: 8.19.75.217, 206.72.242.124, and 206.72.242.162. Organizations are urged to block these addresses where appropriate and to check historical logs for any prior connections from them.

What Administrators Should Do Now

Patches are already available and should be applied immediately:

• Upgrade to VCO 5.2.3.14, 6.1.3.4, 6.4.2.4, or 7.0.0.1, whichever release train applies
• Customers on unsupported release trains should contact the Arista Technical Assistance Center for upgrade guidance
• Until patched, restrict access to the VCO web interface to trusted administrative networks only
• Monitor for suspicious inbound requests, unexpected outbound HTTP/HTTPS traffic, unexplained configuration changes, and unusual maintenance operations

Because a compromised orchestrator can expose every VeloCloud Edge device it manages, incident responders investigating a suspected breach should preserve logs before remediating, then rotate credentials, validate the state of managed edge devices, review administrator action history, and restore systems only from trusted backups. Given the maximum severity score and confirmed in-the-wild exploitation, organizations running on-premises VeloCloud Orchestrator should treat this as an emergency patching priority rather than routine maintenance.

Why SD-WAN Management Planes Are a High-Value Target

Orchestration platforms like VCO sit in an unusually privileged position. A single console typically has visibility into, and control over, every branch office, data center, and cloud gateway connected through the SD-WAN fabric it manages. That centralization is exactly what makes SD-WAN attractive to enterprises in the first place, but it also means a single unpatched command injection flaw can hand an attacker a blueprint of an organization’s entire wide-area network topology, along with the certificates and configuration data needed to intercept or redirect traffic across it.

Command injection bugs like CVE-2026-16812 are also attractive to attackers because they tend to be reliable and repeatable. Unlike memory-corruption vulnerabilities, which often require careful exploitation and can be brittle across patch levels, a CWE-78 flaw generally just requires finding the right parameter that gets passed unsanitized into a system shell. That makes the vulnerability class a favorite for both opportunistic scanning campaigns and more targeted intrusions, and it explains why researchers observed exploitation attempts arriving quickly once the flaw’s existence became apparent.

The fact that this particular flaw requires no authentication only widens the pool of potential attackers, since any actor capable of reaching a vulnerable orchestrator’s web interface, whether through direct internet exposure, a compromised VPN, or lateral movement from elsewhere in the network, can attempt exploitation without first having to steal or guess valid credentials. Enterprises that rely on Arista’s on-premises VeloCloud Orchestrator should treat this incident as a reminder to periodically reassess whether management interfaces for network infrastructure genuinely need to be reachable from outside a tightly controlled administrative segment at all.