CVE-2026-17191: VeloCloud Orchestrator Flow Metrics API SQL Injection
An input validation vulnerability exists in an API component of the orchestrator. An authenticated user can exploit this flaw to manipulate backend queries, which may result in unauthorized access to data beyond their intended privileges and cause the underlying system to initiate unintended outbound network connections.
This issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.
Security readout for executives and security teams
Plain-English summary
VeloCloud Orchestrator On-Prem contains a critical flaw in its Flow Metrics API. A logged-in user with limited privileges could manipulate database queries, access information outside their authorization, alter data, disrupt service, and trigger unintended outbound connections from the orchestrator.
Executive priority
Treat as an urgent remediation item where an affected on-prem version is deployed. Prioritize internet-accessible or broadly reachable orchestrators and environments with many delegated users. The authentication requirement reduces exposure, but credential compromise or malicious insiders could still produce significant data loss.
Technical view
CVE-2026-17191 is an authenticated SQL injection vulnerability, classified as CWE-89, in an orchestrator API component. Network access, low complexity, low privileges, and no user interaction are required. Its CVSS 3.1 score is 9.1, with high confidentiality impact, low integrity and availability impact, and changed scope.
Likely exposure
Exposure is limited to VeloCloud Orchestrator On-Prem versions 5.2.0, 6.1.0, and 6.4.0 according to the supplied record. Other versions have a default status of unaffected. Practical risk depends on whether untrusted or compromised authenticated users can reach the affected API.
Exploitation context
The supplied record is not marked as CISA KEV, and Arista states it is unaware of malicious use in customer networks. Exploitation nevertheless requires only authenticated, low-privilege API access and could cross authorization boundaries. No public exploit evidence is provided in the source bundle.
Researcher notes
The changed-scope rating reflects potential effects beyond the vulnerable API, including unintended outbound connections. The sources do not describe the vulnerable parameters, affected database technology, patch versions, indicators of compromise, or a proof of concept. Testing should remain authorized and non-destructive.
Mitigation direction
Identify any on-prem orchestrators running versions 5.2.0, 6.1.0, or 6.4.0.
Consult Arista Security Advisory 0145 for vendor-approved remediation and fixed-version guidance.
Restrict affected API access to trusted administrative networks and authenticated users.
Review and remove unnecessary orchestrator accounts or privileges.
Monitor orchestrator-originated outbound connections until remediation is confirmed.
Validation and detection
Confirm deployed product edition and exact orchestrator version.
Verify remediation status against Arista Security Advisory 0145.
Review Flow Metrics API activity for unusual authenticated requests or authorization-boundary violations.
Investigate unexpected database errors associated with API requests.
Review outbound network telemetry from the orchestrator for unexplained destinations.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.