Arista Warns of Exploited VeloCloud Orchestrator RCE
Tech GuruQuick Answer
The authority published Security Advisory 0183 for VeloCloud Orchestrator on-prem, hosted, and dedicated deployments in affected 5.2, 6.1, 6.4, and 7.0 release trains. Arista disclosed an unauthenticated command-injection flaw in VeloCloud Orchestrator and states that it is being actively exploited. Hosted services were patched; some on-prem release trains still show fixes pending. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory VeloCloud Orchestrator on-prem, hosted, and dedicated deployments in affected 5.2, 6.1, 6.4, and 7.0 release trains, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-09-22 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | VeloCloud Orchestrator on-prem, hosted, and dedicated deployments in affected 5.2, 6.1, 6.4, and 7.0 release trains |
|---|---|
| Advisory | Security Advisory 0183 |
| CVE | CVE-2026-93952 |
| Authoritative release date | 2026-09-22 07:37:24.300 UTC |
| Authority revision date | 2026-09-22 13:14:07.101 UTC |
| Affected versions | On-prem VCO 5.2.3.15 and earlier, 6.1.3.7 and earlier, 6.4.2.7 and earlier, and 7.0.0.2 and earlier; Arista states that hosted and dedicated services were affected but patched. |
| Fixed version | VCO 5.2.3.16 or 6.4.2.8 where available; fixes for the other listed trains are pending, so follow Arista's current remediation table |
| CVSS base score | 10.0 (CVSS v3.1) / 9.5 (CVSS v4.0) |
| CVSS severity | Critical |
| Exploitation status | Known exploited: Arista states that CVE-2026-93952 is being actively exploited; no exploitation claim is inferred. |
What Changed
Arista disclosed an unauthenticated command-injection flaw in VeloCloud Orchestrator and states that it is being actively exploited. Hosted services were patched; some on-prem release trains still show fixes pending.
What To Validate Now
- Inventory. Locate VeloCloud Orchestrator on-prem, hosted, and dedicated deployments in affected 5.2, 6.1, 6.4, and 7.0 release trains deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: On-prem VCO 5.2.3.15 and earlier, 6.1.3.7 and earlier, 6.4.2.7 and earlier, and 7.0.0.2 and earlier; Arista states that hosted and dedicated services were affected but patched. Do not infer applicability from product family or severity alone.
- Remediate. Apply VCO 5.2.3.16 or 6.4.2.8 where available; fixes for the other listed trains are pending, so follow Arista's current remediation table through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
