---
id: CVE-2026-114625
title: Security Advisory 0199
summary: >-
  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,
  integ…
severity: critical
cvss: 9.9
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'
cvssSource: cna
cwe:
  - CWE-89
vendor: Arista Networks
product: VeloCloud Orchestrator
affected:
  - velocloud_orchestrator >= 5.2.0 < 5.2.3.18
  - velocloud_orchestrator >= 6.1.0 < 6.1.3.10
  - velocloud_orchestrator >= 6.4.0 < 6.4.2.12
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-10-22T23:06:06.826012Z'
published: '2026-10-22'
updated: '2026-10-23'
sourceUpdated: '2026-10-23T03:55:37.265Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-114625'
references:
  - url: >-
      https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199
    label: Security Advisory 0199
tags:
  - cve.org
ingestedAt: '2026-10-22T22:00:50.432Z'
---

## Overview

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.

On an affected system, any authenticated user can gain operator privileges and masquerade as a local "superuser operator" user. This includes access to functionality that is intended for internal use only and which is not intended to be remotely accessible.

Hosted, including Dedicated, versions of VCO were impacted and have already been patched.

## Affected

- `velocloud_orchestrator >= 5.2.0 < 5.2.3.18`
- `velocloud_orchestrator >= 6.1.0 < 6.1.3.10`
- `velocloud_orchestrator >= 6.4.0 < 6.4.2.12`

## Remediation

The recommended resolution is to upgrade to a fixed VCO release at your earliest convenience.

These vulnerabilities have been fixed in the following releases:

- VCO 5.2.3.18 and later in the 5.2 train
- VCO 6.1.3.10 and later in the 6.1 train
- VCO 6.4.2.12 and later in the 6.4 train

### Workarounds

Until the fixed software is deployed, operators should apply defense-in-depth controls appropriate for their environment:

- Restrict access to the VCO web interface to trusted administrative networks.
- Monitor the VCO for accesses from known malicious source IPs.
- Monitor for unexpected outbound network activity from the VCO host.
- Consider blocking outbound ports not needed for normal activities.
- Monitor for backdoor daemons and webshells.
- Review recent administrator activity for unexpected changes.