Arista
VeloCloud Orchestrator
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-93952 | 22 Sep 2026 | VeloCloud Orchestrator (VCO) On-Prem: 5.2.0 ≤ 5.2.3.15, 6.1.0 ≤ 6.1.3.7, 6.4.0 ≤ 6.4.2.7, 7.0.0 ≤ 7.0.0.2 | The recommended resolution is to upgrade to a remediated VCO software version at your earliest convenience. These vulnerabilities have been fixed in the following releases:; - VCO 5.2.3.16 and later in the 5.2.3 train; - VCO 6.4.2.8 and later in the 6.4.2 train; Releases in other release trains that fix this will be added over time. For VCOs not on a supported release train, customers can contact TAC to discuss possible upgrade options. | Update reference ↗ |
| CVE-2026-16812 | 27 Jul 2026 | VeloCloud Orchestrator On-Prem: 5.2.0 < 5.2.3.14, 6.1.0 < 6.1.3.4, 6.4.0 < 6.4.2.4, 7.0.0 < 7.0.0.1 | The recommended resolution is to upgrade to a fixed VCO release at your earliest convenience.; This vulnerability has been fixed in the following releases:; * VCO 5.2.3.14 and later in the 5.2 train; * VCO 6.1.3.4 and later in the 6.1 train; * VCO 6.4.2.4 and later in the 6.4 train | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.