2026-07-28 · view entry permalink →
CVE-2026-16812 — Arista VeloCloud Orchestrator on-prem: unauthenticated OS command injection on an interface exposed by default, confirmed exploited (CVSS 10.0)
Arista disclosed CVE-2026-16812 on 2026-07-27: an improper-neutralisation flaw (CWE-78, OS command injection) in on-prem VeloCloud Orchestrator (VCO) that lets a remote attacker reach "privileged internal functionality" and act on the orchestrator host, scored 10.0 on both CVSS 3.1 and CVSS 4.0 (Arista, 2026-07-27). Two properties make this worse than the score alone suggests. First, there is no exploitation precondition to remove: Arista states the interface "is exposed by default", that "[t]here is no configuration that can prevent the exposure", and that tenant or operator credentials are not required — the only reachability control is network placement (Arista, 2026-07-27). Second, VCO is a management plane, not an edge device: Arista's own post-remediation guidance warns that "[c]ompromises to the VCO platform may allow attackers access to the VeloCloud Edge devices as well", so the blast radius is the managed SD-WAN fleet rather than one appliance (Arista, 2026-07-27).
Exploitation is not a projection. Arista states the issue "was discovered externally and is known to be actively exploited", and CISA added CVE-2026-16812 to the Known Exploited Vulnerabilities catalog on the day of disclosure (CISA, 2026-07-27). Affected are on-prem VCO 5.2.x before 5.2.3.14, 6.1.x before 6.1.3.4, 6.4.x before 6.4.2.4 and 7.0.x before 7.0.0.1; Arista's Resolution section enumerates fixed builds for the 5.2, 6.1 and 6.4 trains only, so 7.0.x operators should confirm their target release with the vendor rather than assume one. Hosted and Dedicated orchestrators were patched ahead of the advisory, and VeloCloud Gateway, VeloCloud Edge and the Arista EOS-based product lines are not in scope (Arista, 2026-07-27).
Detection, telemetry class first: the orchestrator's own web-access and reverse-proxy logs are the primary surface — Arista directs operators to requests carrying unusual URL-like path components, encoded characters or references to local or internal services, and to elevated request rates against the management interface. Pair that with backend application and system logs around the same timestamps for command execution, file creation, database export or archive artifacts that no administrator session accounts for, and with egress telemetry for outbound HTTP/HTTPS originating from the orchestrator host itself (Arista, 2026-07-27). The discriminator that carries the most weight here is directionality and provenance rather than payload shape: a management appliance legitimately receives administrative sessions and pushes configuration to its managed Edge devices, but it has little reason to originate arbitrary outbound web traffic, and configuration changes or privileged maintenance actions that correlate to no operator session are the anomaly Arista itself flags — the vendor states plainly that no single definitive indicator of compromise exists for this issue, so sequence and correlation carry the detection rather than any one artifact. Hardening is limited to what network placement can buy: Arista's interim control is restricting the web interface to trusted administrative networks, since the exposed functionality cannot be switched off in configuration.
This issue was discovered externally and is known to be actively exploited.
VCO is exposed by default. There is no configuration that can prevent the exposure. A successful attack requires network access to the VCO web interface. VCO tenant or operator credentials are not required for this exposure.
Compromises to the VCO platform may allow attackers access to the VeloCloud Edge devices as well.