Skip to content
NewA calmer, faster ZeroHour
VulnerabilityKEV6 · 1 read

CVE-2026-93952

Unauthenticated Input-Validation Flaw in VeloCloud Orchestrator (On-Prem)

CISA: Arista VeloCloud Orchestrator Improper Input Validation Vulnerability

CVSS 4.0
9.5 critical
EPSS
1%p72
Published
·
Added to KEV
Analyze CVE-2026-93952 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

An improper input validation flaw (CWE-20) in the on-premises VeloCloud Orchestrator (VCO) allows a remote, unauthenticated attacker to reach privileged internal functionality on the orchestrator host. Exploitation occurs over the network with no credentials or user interaction (attack complexity is high), and success compromises the confidentiality, integrity, and availability of the orchestrator and the data it manages; the CVSS 4.0 vector also flags high impact on subsequent systems, meaning the SD-WAN edges and sites the orchestrator controls are at risk. Affected deployments are customer-operated on-prem VCO installations, while the vendor-hosted (including Dedicated) VCO service was also impacted but has already been patched. No public proof of concept or in-the-wild exploitation has been reported, and the issue is not on CISA's KEV list.

What to do: Update on-prem VCO to the fixed release specified in the Arista/Broadcom security advisory as soon as possible. Until patched, remove internet exposure by placing the orchestrator behind a VPN or IP allowlist, and audit logs for unauthenticated or anomalous API requests. Confirm hosted/Dedicated tenancies are on the current patched build and review managed edge devices for unauthorized configuration changes.

ProductAffected
Arista (VeloCloud; formerly VMware/Broadcom) VeloCloud Orchestrator (VCO), on-premises—
Arista (VeloCloud) VeloCloud Orchestrator — Hosted and DedicatedImpacted, but vendor-hosted instances have already been patched
Estimated exposure
niche≈ several hundred internet-exposed on-prem VCO instances (order 10^2–10^3 total on-prem installs), each managing many SD-WAN edge devices — Most VeloCloud customers use the vendor-hosted orchestrator, and public internet scans typically show only a few hundred exposed VCO management portals, so the at-risk population is small in count but each instance is a critical control…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

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.

KEVCISA Known Exploited Vulnerability
Affected
Arista VeloCloud Orchestrator
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.
Due date
Ransomware use
Unknown
Vendors
arista
Products
velocloud orchestrator
Weakness
CWE-20
Vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

In the news

10 stories