Security Advisory 0199 .CSAF
Date: October 22, 2026
| Revision | Date | Changes |
|---|---|---|
| 1.0 | October 22, 2026 | Initial release |
The CVE-ID tracking this issue: CVE-2026-114625
CVSSv3.1 Base Score: 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)
CVSSv4.0 Base Score: 9.4 (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H)
Common Weakness Enumeration: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
This vulnerability is being tracked by BUG2043622
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.
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.
This issue was detected by Arista and is known to be actively exploited.
Vulnerability Assessment
Platform and Software Applicability Note
To determine actual exposure, operators should first check their software versions against the "Affected Software" list below. If your software release is not listed, your deployment is not vulnerable, regardless of the hardware platform in use.
Affected Software
- VCO 5.2.x releases prior to 5.2.3.18
- VCO 6.1.x releases prior to 6.1.3.10
- VCO 6.4.x releases prior to 6.4.2.12
Note: End of support software versions have not been assessed.
Affected Platforms
- VeloCloud Orchestrator On-Prem (Formerly VeloCloud Orchestrator by Broadcom)
- Arista EOS-based products:
- 710 Series
- 720D Series
- 720XP/722XPM Series
- 750X Series
- 7010TX Series
- 7020R/R4 Series
- 7130 Series running EOS
- 7170 Series
- 7050X3/X4 Series
- 7060X/X2/X4/X5/X6 Series
- 7260X/X3 Series
- 7280R/R2/R3/R4 Series
- 7300X/X3 Series
- 7320X Series
- 7358X4 Series
- 7368X4 Series
- 7388X5 Serie
- 7500R/R2/R3 Series
- 7800R3/R4 Series
- 7700R4 Series
- AWE 5000 Series
- AWE 7200R Series
- ZTX-7200 Series
- CloudEOS
- cEOS-lab
- vEOS-lab
- CloudVision eXchange, virtual or physical appliance
- Wi-Fi Access Points
- CloudVision CUE cloud service delivery
- CloudVision Portal, virtual appliance or physical appliance (including the CV-CUE on premises software)
- CloudVision Appliance Software
- CloudVision as-a-Service
- CloudVision AGNI - Cloud service delivery
- CloudVision AGNI - Virtual or physical appliance
- Arista 7130 Systems running MOS
- Arista Converged Cloud Fabric (formerly Big Switch BCF)
- DANZ Monitoring Fabric (DMF) - Controller Appliance
- DANZ Monitoring Fabric (DMF) - Analytics Node Appliance
- DANZ Monitoring Fabric (DMF) - Recorder Node Appliance
- DANZ Monitoring Fabric (DMF) - Service Node Appliance
- Arista Multi Cloud Director (formerly Big Switch MCD)
- Arista Network Detection and Response (NDR) Security Platform (Formerly Awake NDR)
- Arista Edge Threat Management - Arista NG Firewall and Arista Micro Edge (Formerly Untangle)
- Arista NetVisor OS, Arista NetVisor UNUM, and Insight Analytics (Formerly Pluribus)
- VeloCloud Gateway (Formerly VeloCloud Gateway by Broadcom)
- VeloCloud Edge (Formerly VeloCloud Edge by Broadcom)
Required Configuration for Exploitation
VCO is exposed by default. A successful attack requires network access to the VCO web interface and a valid authenticated session on the VCO portal. The minimum user role required is Enterprise Read Only, the lowest built-in tenant role. There is no configuration that can prevent the exposure.
Indicators of Compromise
Operators should review VCO web access logs for unexpected activity. Requests containing unusual URL-like path components, encoded characters, references to local or internal services, or high request rates should be investigated.
- 74.82.197.86
- 38.54.50.151
If compromise is suspected, operators should preserve VCO web access logs, backend application logs, system logs, database logs, and relevant file-system timestamps before remediation where operationally feasible.
Mitigation
The recommended resolution is to upgrade to a fixed VCO release as soon as it is available. For VCOs which are not on a supported release train, customers can contact TAC to discuss possible upgrade options for your release.
- 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.
Resolution
The recommended resolution is to upgrade to a fixed VCO release at your earliest convenience.
- 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
For More Information
If you require further assistance, or if you have any further questions regarding this security notice, please contact the Arista Networks Technical Assistance Center (TAC) by one of the following methods:
Open a Service Request
Contact information needed to open a new service request may be found at:
https://www.arista.com/en/support/customer-support
