CVE-2026-16812
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Summary
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Arista Networks | VeloCloud Orchestrator On-Prem | 5.2.0 < 5.2.3.14 | affected |
| Arista Networks | VeloCloud Orchestrator On-Prem | 6.1.0 < 6.1.3.4 | affected |
| Arista Networks | VeloCloud Orchestrator On-Prem | 6.4.0 < 6.4.2.4 | affected |
| Arista Networks | VeloCloud Orchestrator On-Prem | 7.0.0 < 7.0.0.1 | affected |
Weaknesses
- CWE-78: CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Workarounds
The recommended resolution is to upgrade to a fixed VCO release as soon as it is available. For VCOs which are not on a supported release train, customers can contact TAC to discuss possible upgrade options for your release.
Until the fixed software is deployed, operators should apply defense-in-depth controls appropriate for their environment:
Restrict access to the VCO web interface to trusted administrative networks.
Monitor the VCO for accesses from known malicious source IPs.
Monitor for unexpected outbound network activity from the VCO host.
Review recent administrator activity for unexpected changes.
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: active
- Automatable: yes
- Technical Impact: total
Additional References
References
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.