CVE-2026-114625: Arista VeloCloud Orchestrator SQL Injection
Arista VeloCloud Orchestrator · listed in the CISA catalog of actively exploited vulnerabilities since 2026-10-23.
- CVSS v3.1 (CVE record)
- 9.9
- critical
- EPSS (exploit probability, 30 days)
- 7.7%
- higher than 94.7% of all CVEs
- Added to CISA KEV
- 2026-10-23
- US federal due date 2026-10-26
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2026-114625 explained
CVE-2026-114625 is an SQL injection vulnerability (CWE-89) in Arista VeloCloud Orchestrator (VCO) on-prem. Any authenticated user can gain operator privileges, masquerade as a local "superuser operator" and reach internal-only functionality. CISA lists it as known exploited, so on-prem deployments need urgent patching.
Impact
A remote attacker with a low-privileged account can gain operator privileges and access internal functionality not meant to be remotely reachable. No user interaction is needed. Successful exploitation can compromise the confidentiality, integrity and availability of the orchestrator, the data it manages and the VCO host. The impact extends beyond the vulnerable component. CISA rates the technical impact as total but not automatable. Attackers are known to exploit it.
Who is affected
Arista Networks VeloCloud Orchestrator On-Prem is affected in three branches: ≥ 5.2.0, < 5.2.3.18, ≥ 6.1.0, < 6.1.3.10 and ≥ 6.4.0, < 6.4.2.12. The fixed versions are 5.2.3.18, 6.1.3.10 and 6.4.2.12. According to the description, hosted VCO versions, including Dedicated, were also impacted and have already been patched.
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Arista Networks VeloCloud OrchestratorVeloCloud Orchestrator On-PremAffectedFixed in
- ≥ 5.2.0, < 5.2.3.18
- ≥ 6.1.0, < 6.1.3.10
- ≥ 6.4.0, < 6.4.2.12
- 5.2.3.18
- 6.1.3.10
- 6.4.2.12
| Product | Affected | Fixed in |
|---|---|---|
| Arista Networks VeloCloud OrchestratorVeloCloud Orchestrator On-Prem |
|
|
How to fix it
- Update to a fixed version: 5.2.3.18, 6.1.3.10, 6.4.2.12.
- Vendor advisory: arista.com/en/support/advisories-notices/security-advisor…
- CISA's deadline for US federal agencies: 2026-10-26 (passed) – a useful benchmark for everyone else, too.
Vendor solution:
- 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
Workaround: 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.
What to do
- Upgrade on-prem VCO to
5.2.3.18,6.1.3.10or6.4.2.12, matching your branch. - Apply any mitigations in the Arista vendor advisory until the upgrade is complete.
- Restrict network access to the orchestrator and keep it off the internet where possible.
- Review user accounts and remove unneeded or untrusted accounts, since any authenticated user can exploit this.
- Check for signs of compromise, such as unexpected operator-level activity, following CISA's forensics triage requirements.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Questions about CVE-2026-114625
- Are hosted VeloCloud Orchestrator instances affected?
- According to the CVE description, hosted versions of VCO, including Dedicated, were impacted and have already been patched. Customers running VCO on-prem must upgrade it themselves.
- Does an attacker need an account?
- Yes. Low privileges are required. Any authenticated user on an affected system can gain operator privileges and act as a local "superuser operator".
- Is this vulnerability exploited in the wild?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-10-23, with a US federal due date of 2026-10-26. Whether it has been used in ransomware campaigns is unknown.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.