Arista's advisory for CVE-2026-114625 contains one sentence that changes how defenders should plan: VCO is exposed by default, and no VCO setting prevents the exposure. The management interface is meant to be reachable, because partners and customers use it from wherever they work.
For a 9.9-rated SQL injection that escalates a read-only login to operator, that design choice sets the terms of the response.
The exposure model
In VeloCloud SD-WAN, the orchestrator is the control point. Operators create customer accounts, partners manage groups of customers, and the web interface is the interface through which both groups operate the network. Arista notes that exploitation requires network access to that interface and a valid login at Enterprise Read Only or above.
Both prerequisites are ordinary in enterprise deployments. A partner account that manages dozens of customers is a normal business arrangement. A read-only account is the account type an auditor or a monitoring integration might hold. The flaw gives that account the operator role.
The earlier VCO bugs show a different pattern. CVE-2026-16812 in July and CVE-2026-93952 in September needed no login at all, and the September flaw carried a CVSS score of 10.0. CVE-2026-114625 adds an authentication requirement and keeps a comparable severity, which suggests the impact of the post-authentication action is heavy enough to offset the added precondition.
What exposure actually means in a query result
ZoomEye reports 529 assets matching title="VeloCloud". That is a measure of how much VeloCloud-branded web surface is visible on the internet. It is not a vulnerability count. A matching host may run a patched build, may be a hosted tenant that Arista already fixed on its own infrastructure, or may be a login page for a deployment whose orchestrator sits elsewhere.
Queries that tried to narrow to application fingerprints returned zero in this check, so the broader title match is the honest description of what is visible. Treat the number as a planning input for where to look, not as an impact assessment.
Practical consequences for defenders
If the interface cannot be hidden, the useful controls are network placement and identity:
Put the orchestrator behind a management network, VPN or allow-list so that only administrative sources can open the web interface.
Inventory every account with web access, including partner accounts and read-only service accounts, and remove the ones nobody can justify.
Treat an Enterprise Read Only account as a potential path to operator rights until the fixed release is installed.
Arista's own interim guidance follows the same logic: limit access to the VCO web interface to trusted administrative networks, monitor for connections from known malicious addresses, and watch for unexpected outbound traffic from the VCO host.
The detection side
Two addresses have been observed in the attacks according to the advisory: 74.82.197[.]86 and 38.54.50[.]151. Blocking them is the easy step. Reading the logs is the harder one.
The advisory suggests looking at VCO web access logs for requests that contain unusual URL-like path components, encoded characters, references to local or internal services, or a high request rate. Those patterns describe someone probing an injection point. Because the flaw is a SQL injection behind an authenticated interface, requests may arrive with a valid session and look ordinary at the authentication layer. The payload is in the parameters.
If compromise is suspected, Arista advises preserving evidence before remediation: VCO web access logs, backend application logs, system logs, database logs and file-system timestamps.
Versions in scope
On-premises orchestrators are affected below 5.2.3.18 on the 5.2 train, below 6.1.3.10 on 6.1, and below 6.4.2.12 on 6.4. Hosted and Dedicated orchestrators were patched by Arista. VeloCloud Gateway and VeloCloud Edge are not affected. The 7.0 train is not listed, and Arista states that releases absent from the list are not vulnerable. End-of-support releases were not evaluated, so an old train needs a conversation with Arista TAC rather than an assumption.
Builds that fixed the July and September flaws are still affected here. A team that patched in September has work to do again.
A note on the patch question
The advisory does not say whether upgrading removes access an attacker already obtained, and it does not say whether a compromised orchestrator still exposes edge devices as it did in the two earlier incidents. Both questions decide whether patching is the end of the response or the beginning of one. Where the answer is unknown, verify the operator tier and review administrator activity rather than assuming the upgrade closed the incident.
Sources
Arista Security Advisory 0199: https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199
Arista Security Advisory 0183: https://www.arista.com/en/support/advisories-notices/security-advisory/24765-security-advisory-0183
The Hacker News report: https://thehackernews.com/2026/10/arista-warns-of-critical-velocloud-sql.html