Actively exploited in the wild
Arista VeloCloud Orchestrator On-Prem OS Command Injection Vulnerability
Arista - VeloCloud Orchestrator · Listed in the CISA KEV since 2026-07-27. This indicates confirmed attacks in production environments.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CVE-2026-16812
CriticalCVSS 10.0KEVExploitation Probability (EPSS)
Elevated risk59th percentile - higher than 59% of all known CVEs
Summary
VeloCloud Orchestrator (VCO) on-prem has a vulnerability that allows a remote attacker to access privileged internal functionality, impacting the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and managed data. This issue is actively exploited.
Risk Assessment
A remote attacker can gain unauthorized access to internal VCO functions, potentially leading to full compromise of the orchestrator and its managed data.
Recommendation
Immediately apply patches provided by VMware for VCO (Hosted and Dedicated versions are already patched) and restrict network access to VCO.
Original NVD description (English source)
VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator. This functionality was intended to be for internal use only and is not intended to be remotely accessible. Hosted and Dedicated versions of VCO have already been patched in advance of this notice going out. This issue was discovered externally and is known to be actively exploited.