CVE-2026-93952
Arista VeloCloud Orchestrator Improper Input Validation
- Published22 Sept 2026
- Added to CISA KEV22 Sept 2026
- Remediation due25 Sept 2026
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 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-93952 being actively exploited?
Yes. CVE-2026-93952 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 22 Sept 2026.
How severe is CVE-2026-93952?
CVE-2026-93952 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 1.06% probability of exploitation.
Which products are affected by CVE-2026-93952?
Affected products include Arista Velocloud Orchestrator.
How do I fix CVE-2026-93952?
Upgrade affected software to a fixed version, for example Arista Velocloud Orchestrator 5.2.3.16 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-93952 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.