
Actively exploited • authenticated SQL injection[1]
Arista patches actively exploited VeloCloud Orchestrator flaw CVE-2026-114625[1]
Arista says CVE-2026-114625 is an actively exploited SQL injection vulnerability in on-premises VeloCloud Orchestrator. A valid VCO session is required, but the lowest built-in tenant role—Enterprise Read Only—is sufficient to reach the vulnerable path and gain operator privileges.[1]
Reporting cutoff: 2026-10-23T20:46:47Z. The Arista advisory was re-fetched in a rendered browser and CISA KEV JSON was checked separately; the CVE Program API capture remains from October 22.[1][2][3]
Practical guidance: Decision for administrators
Editorial/practical guidance: If you run VCO on-premises in an affected branch, treat this as an urgent patch-and-investigate event. Arista says hosted and dedicated VCO deployments were affected but have already been patched.[1]
Arista advises preserving relevant logs and file-system timestamps before remediation where compromise is suspected.[1] Editorial/practical guidance: Patching closes the vulnerable path but does not prove an intruder is absent.
Evidence: Exactly what is exposed[1]
The exposure predicate is: an on-premises VCO release below the fixed build in a listed branch, a network path to the VCO web interface, and a valid authenticated VCO portal session. VCO is exposed by default, and Arista says no configuration can prevent the exposure. Enterprise Read Only is the minimum required role.[1]
| Branch | Affected | Fixed release |
|---|---|---|
| 5.2.x | Earlier than 5.2.3.18 | 5.2.3.18 or later in 5.2[1] |
| 6.1.x | Earlier than 6.1.3.10 | 6.1.3.10 or later in 6.1[1] |
| 6.4.x | Earlier than 6.4.2.12 | 6.4.2.12 or later in 6.4[1] |
Arista says end-of-support releases were not assessed. VeloCloud Gateway and VeloCloud Edge are listed as not affected.[1]
Evidence: What Arista observed[1]
Arista says it detected the issue and knows it is being actively exploited. It published two attack-source addresses: 74[.]82[.]197[.]86 and 38[.]54[.]50[.]151. These are defensive indicators, not proof by themselves that a system was compromised.[1]
At the reporting cutoff, the retained Arista CNA CVE record remained the stated published CVE 5.2 record. Its metadata names Arista as assigner/CNA, marks the record PUBLISHED, and gives 2026-10-22T20:47:56.427Z for publication and update. The CNA container lists on-premises VeloCloud Orchestrator affected from 5.2.0 to before 5.2.3.18, from 6.1.0 to before 6.1.3.10, and from 6.4.0 to before 6.4.2.12; it gives CVSS v3.1 9.9/CRITICAL and CVSS v4.0 9.4/CRITICAL. Its source field says discovery was EXTERNAL, while Arista’s advisory says Arista detected the issue; the sources do not explain that wording difference. The CVE record omits the advisory’s active-exploitation statement, two attack-source addresses and evidence-preservation guidance, so use the advisory for those facts.[3] CISA KEV catalog version 2026.10.23 (released 2026-10-23T19:30:18.9209Z) contains one exact entry for CVE-2026-114625. It was added on 2026-10-23 with a due date of 2026-10-26, forensic triage marked Yes, and known ransomware campaign use marked Unknown. Its required action points to vendor mitigations and BOD 26-04 guidance.[2] For U.S. Federal Civilian Executive Branch agencies, KEV remediation timeframes are required under BOD 26-04; CISA says other organizations are not bound by the directive and recommends that they prioritize KEV remediation.[2]
Practical guidance: Check safely, then contain and patch
- Editorial/practical guidance: Identify the running VCO build and deployment model. Do not classify a hosted service or an end-of-support release from the supported on-premises table.
- Preserve evidence first when compromise is plausible. Arista names VCO web-access, backend-application, system and database logs plus relevant file-system timestamps.[1]
- Apply defense in depth while patching. Restrict the VCO web interface to trusted administrative networks; monitor the two published source addresses, unexpected outbound activity, backdoor daemons, webshells and recent administrator changes. Arista presents these as interim controls, not a configuration fix.[1]
- Upgrade every on-premises instance to its branch’s fixed build or later. Contact Arista TAC for unsupported-release upgrade options.[1]
Practical guidance: Verify the outcome
Editorial note: The four checks below are practical editorial guidance derived from Arista’s fixed-release, defensive-control and investigation guidance; Arista does not state these exact validation steps.[1]
- Editorial/practical guidance: Confirm the active VCO build—not only downloaded media—meets the fixed threshold.
- Editorial/practical guidance: Confirm every VCO node or replica was updated and old instances are no longer serving traffic.
- Editorial/practical guidance: Recheck effective administrative-network restrictions, inbound and outbound telemetry, administrator activity and the preserved logs.
- Editorial/practical guidance: If investigation finds unauthorized operator activity, backdoors or webshells, treat this as an incident: patching alone does not evict an attacker.
Sources
- Arista Security Advisory 0199 (October 22, 2026).
- CISA Known Exploited Vulnerabilities Catalog (version 2026.10.23; CVE-2026-114625 added 2026-10-23, due 2026-10-26, forensic triage Yes, ransomware use Unknown; BOD 26-04 binds FCEB agencies, while CISA recommends KEV prioritization to other organizations).
- CVE Program API — CVE-2026-114625 (published CVE 5.2 record from the Arista CNA; retained capture observed 2026-10-22T20:54:52.713476Z).
