CVE-2026-93952
🔴 High In CISA KEVArista Networks 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
CVSS (Koffei note)
10.0CVSS (v3.1, CVE List)
10.0EPSS (2026-11-18)
1.384%72.75th percentile
CISA KEV
2026-09-22due 2026-09-25
Exploitation
Yes — CISA KEV since 22/09/2026 (SSVC 22/09/2026: exploitation active, automatable yes, technical impact total). No attribution, no published IOCs
Timeline
- 22/09/2026Added to the CISA KEV catalogue
- 22/09/2026CVE record published (CVE List)
- 23/09/2026Arista VeloCloud Orchestrator CVSS 10.0 flaw (CVE-2026-93952)
- 25/09/2026Arista VeloCloud Orchestrator max-severity flaw actively exploited
- 25/09/2026CISA deadline for US federal agencies
- 28/09/2026VeloCloud Orchestrator flaw hits CVSS 10.0, actively exploited
- 26/10/2026Arista VeloCloud Orchestrator SQL injection, third flaw exploited since July
Risk
10.0 Critical (v3.1, Arista CNA) / 9.5 (v4.0) — AV:N/AC:L/PR:N/UI:N, EPSS 1.384% (improper input validation → authentication bypass and access to privileged functions ; exposure requires certificate-based Edge-to-VCO authentication to be configured and the public part of an Edge certificate, which is why v4.0 scores AC:H and lands at 9.5 against v3.1's 10.0)
Fix
Yes — VCO 5.2.3.16 / 6.4.2.8 and later (Arista Security Advisory 0183). No fixed release is listed for the 6.1 or 7.0 trains
Official description
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. Hosted, including Dedicated, versions of VCO were impacted and have already been patched.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWE-20