Skip to content
PiLabs security advisory Updated 2 November 2026
Critical 10.0 CVE-2026-93952 Known exploited

Improper input validation in Arista VeloCloud Orchestrator

Affected
Arista VeloCloud Orchestrator
Affected versions
≥ 5.2.0, < 5.2.3.16; ≥ 6.1.0, ≤ 6.1.3.7; ≥ 6.4.0, < 6.4.2.8; ≥ 7.0.0, ≤ 7.0.0.2
Disclosed
Last updated
CVSS 3.1 vector
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Written automatically on 27 October 2026 from the NVD and the CISA catalogue of known exploited vulnerabilities. The facts above come from those sources; check them before you act. Updated by Pinet on 2 November 2026. Sources of this advisory

Arista reports an improper input validation flaw in on-premises VeloCloud Orchestrator that may let a remote attacker reach privileged internal functionality. CISA lists CVE-2026-93952 as exploited.

What is affected

Arista reports an improper input validation issue (weakness type CWE-20) in the on-premises edition of Arista VeloCloud Orchestrator, also called VCO. The issue is tracked as CVE-2026-93952. According to the sources, the affected on-prem versions are:

  • ≥ 5.2.0, < 5.2.3.16
  • ≥ 6.1.0, ≤ 6.1.3.7
  • ≥ 6.4.0, < 6.4.2.8
  • ≥ 7.0.0, ≤ 7.0.0.2

A range such as < 5.2.3.16 means the versions before 5.2.3.16. Arista states that hosted versions of VCO, including Dedicated, were impacted and have already been patched.

What the flaw allows

The source description says the 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 of the data it manages.

The CVSS version 3.1 base score is 10.0, which is critical severity. The vector in the sources describes an attack over the network with low complexity, with no privileges and no user interaction required, and with a changed scope. The sources give no further technical detail, and none is repeated here.

Exploitation

CISA lists this vulnerability as exploited in its Known Exploited Vulnerabilities catalogue. It was added on 2026-09-22. CISA's stated due date for US federal agencies is 2026-09-25. CISA records known ransomware use as unknown. The sources do not describe who is exploiting the flaw or how.

If you do not run an on-prem VCO, the sources do not point to action on your side for the hosted service, because Arista states that hosted versions have already been patched.

What to do

First establish whether you operate an on-prem Arista VeloCloud Orchestrator and, if so, which version it runs. Compare that version with the ranges above. Arista's security advisory is the place to confirm exposure and it lists the fixed releases. Plan the update with priority, given the critical rating and CISA's listing.

The record for this vulnerability is also available in the NVD, and the CISA catalogue entry shows CISA's required action. Details and links are in the section below.

What to do

Follow the vendor instructions in the Arista security advisory, which lists the fixed releases and how to check exposure. CISA's required action is to apply mitigations in line with vendor instructions, or to stop using the product if mitigations are unavailable. See the CISA Known Exploited Vulnerabilities catalogue and the NVD entry for CVE-2026-93952 for further detail.

Sources

Mentioned in security bulletins

All vulnerabilities

Need to know whether these vulnerabilities affect you?

A consultant can check which of the affected products you run and what to fix first. For a wider review, ask for a security assessment.