Unauthenticated OS Command Injection in Arista VeloCloud Orchestrator
CVE-2026-16812 is an unauthenticated operating system command injection vulnerability in Arista VeloCloud Orchestrator (VCO) On-Prem. Privileged functionality intended only for internal use is remotely reachable through the VCO web interface, allowing an attacker to execute arbitrary operating system commands on the orchestrator host. Affected releases are 5.2.0 before 5.2.3.14, 6.1.0 before 6.1.3.4, 6.4.0 before 6.4.2.4, and 7.0.0 before 7.0.0.1. Exploitation requires neither authentication nor user interaction. The vulnerability is actively exploited and has a CVSS v3.1 and v4.0 score of 10.0. Hosted and Dedicated VCO deployments were patched before public disclosure.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise the confidentiality, integrity, and availability of the orchestrator host and its managed data. Commands execute with the VCO service account's privileges and may permit installation of malicious software, data theft or modification, account creation, and service disruption. Orchestrator compromise can expose SD-WAN configurations, administrative credentials, certificates, cryptographic keys, and management databases. Attackers may also use the orchestrator's trusted management position to access managed VeloCloud Edge devices or distribute unauthorized routing, firewall, VPN, and certificate changes, potentially disrupting connectivity across multiple sites. Edge and Gateway appliances are not directly vulnerable to this flaw.
If you can’t patch tonight, do this now.
Until patching is complete, restrict access to the VCO web interface to trusted administrative networks using upstream firewalls, allowlists, VPN access, or dedicated management networks. No VCO configuration eliminates the underlying vulnerability. Review web access, backend application, system, and database logs for suspicious requests, unexpected command execution, unauthorized administrative or configuration changes, and abnormal outbound connections. Preserve relevant logs and file-system timestamps when compromise is suspected. Network restrictions reduce exposure but do not replace the vendor update.
Patch, then assume compromise.
Immediately upgrade affected VCO On-Prem deployments to a fixed release within the corresponding branch: 5.2.3.14 or later for 5.2.x, 6.1.3.4 or later for 6.1.x, 6.4.2.4 or later for 6.4.x, and 7.0.0.1 or later for 7.0.x. Investigate potentially exposed deployments for prior exploitation; patching alone does not remove an existing compromise. If compromise is suspected, preserve evidence before remediation where feasible, rotate exposed credentials and cryptographic material, remove unauthorized persistence or restore from trusted sources, and validate managed Edge device configurations and state.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
116 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.