Executive Summary
In October 2026, Arista disclosed an actively exploited critical SQL injection zero-day (CVE-2026-114625, CVSS 9.9) in the VeloCloud Orchestrator (VCO), the central management plane for VeloCloud SD-WAN networks. Any authenticated user—even one holding the lowest read-only customer role—could exploit the flaw to escalate to full operator-level privileges, potentially compromising the orchestrator host, its data, and downstream VeloCloud Edge devices. Fixes were released in VCO 5.2.3.18, 6.1.3.10, and 6.4.2.12; cloud-hosted instances were patched by Arista. Two attacker-controlled IPs were observed actively exploiting the vulnerability in the wild before the patch was available.
This is the third VCO zero-day exploited since July 2026, signaling a sustained, targeted campaign against SD-WAN management infrastructure. The pattern—unauthenticated flaws followed by an authenticated privilege-escalation bug—suggests attackers are systematically mapping and chaining VCO weaknesses to achieve persistent, high-privilege control over enterprise network fabrics at scale.
Why This Matters Now
SD-WAN orchestrators are high-value, internet-exposed control planes governing thousands of enterprise branch and cloud sites. Three exploited VCO zero-days in under four months demonstrate that threat actors are prioritizing network management layer compromise as a force-multiplier attack vector. Organizations that have not yet patched—or that lack compensating controls around orchestrator access—face immediate risk of full network takeover and data exposure.
Attack Path Analysis
Attackers with minimal valid credentials (Enterprise Read Only role) exploited a critical SQL injection zero-day (CVE-2026-114625, CVSS 9.9) in Arista VeloCloud Orchestrator to escalate privileges to local superuser, gaining full control over the SD-WAN management plane. From that position, attackers established persistence via backdoor daemons and webshells, moved laterally toward managed Edge devices, exfiltrated orchestrator data and configuration, and positioned for broad SD-WAN infrastructure disruption across all managed customer tenants.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Attackers obtained or used low-privilege Enterprise Read Only credentials to authenticate to the publicly exposed VeloCloud Orchestrator web interface. No elevated access was required to initiate exploitation; the orchestrator is exposed by default and no built-in setting restricts access. Two attacker-controlled IPs (74.82.197[.]86 and 38.54.50[.]151) were observed sending crafted SQL injection payloads via the VCO web interface, exploiting CVE-2026-114625.
Related CVEs
CVE-2026-114625
CVSS 9.9A critical SQL injection vulnerability in Arista VeloCloud Orchestrator (VCO) allows an authenticated user with the minimum Enterprise Read Only role to escalate privileges to operator level, potentially gaining full control of the orchestrator, accessing or modifying managed data, and affecting the VCO host itself.
Affected Products:
Arista Networks VeloCloud Orchestrator (VCO) – 5.2.x before 5.2.3.18, 6.1.x before 6.1.3.10, 6.4.x before 6.4.2.12
Exploit Status:
exploited in the wildCVE-2026-93952
CVSS 10A critical unauthenticated remote code execution vulnerability in Arista VeloCloud Orchestrator (VCO) that does not require any login credentials to exploit, rated CVSS 10.0, allowing full compromise of the orchestrator and potentially connected VeloCloud Edge devices.
Affected Products:
Arista Networks VeloCloud Orchestrator (VCO) – 5.2.x before 5.2.3.16, 6.1.x before 6.1.3.7, 6.4.x before 6.4.2.8
Exploit Status:
exploited in the wildCVE-2026-16812
CVSS 10An unauthenticated remote vulnerability in Arista VeloCloud Orchestrator (VCO) exploited in the wild in July 2026, requiring no valid credentials, enabling attackers to compromise the orchestrator and potentially pivot to connected VeloCloud Edge devices.
Affected Products:
Arista Networks VeloCloud Orchestrator (VCO) – 5.2.x (prior to July 2026 fix), 6.1.x (prior to July 2026 fix), 6.4.x (prior to July 2026 fix)
Exploit Status:
exploited in the wild
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Valid Accounts
Server Software Component: Web Shell
Abuse Elevation Control Mechanism
System Information Discovery
Data Manipulation: Stored Data Manipulation
External Remote Services
Impair Defenses: Disable or Modify Tools
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Timely Patching of Known Vulnerabilities
Control ID: Requirement 6.3.3
NYDFS 23 NYCRR 500 – Access Privileges and Least Privilege
Control ID: Section 500.7
DORA (Digital Operational Resilience Act) – Detection, Response, and Incident Reporting
Control ID: Article 10 — ICT-related Incident Management
CISA Zero Trust Maturity Model 2.0 – Network Access Control and Segmentation
Control ID: Network Pillar — Micro-Segmentation
NIS2 Directive – Vulnerability Handling and Disclosure
Control ID: Article 21 — Cybersecurity Risk Management Measures
ISO/IEC 27001:2022 – Technical Vulnerability Management
Control ID: Annex A 8.8 — Management of Technical Vulnerabilities
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
Critical CVE-2026-114625 SQL injection zero-day in VeloCloud SD-WAN Orchestrator enables privilege escalation to superuser, threatening IT infrastructure management, lateral movement across networks, and full orchestrator compromise with exfiltration risk.
Telecommunications
SD-WAN orchestrator exploitation directly endangers telecom-grade network management platforms; attackers gaining operator-level VCO control can manipulate routing, intercept unencrypted traffic, and pivot to downstream VeloCloud Edge devices at scale.
Financial Services
VeloCloud Orchestrator breach exposes financial institutions running SD-WAN to PCI 4.0 and NIST 800-53 violations; privilege escalation and data exfiltration risks threaten transaction data, compliance posture, and east-west segmentation controls.
Government Administration
Public sector orchestrators face ZTMM and NIST CSF compliance failures as unauthenticated-equivalent VCO exploitation enables superuser access, threatening sensitive administrative data, network integrity, and FISMA-aligned egress security enforcement.
Sources
- Arista Warns of Critical VeloCloud SQL Injection Zero-Day Exploited in Attackshttps://thehackernews.com/2026/10/arista-warns-of-critical-velocloud-sql.htmlVerified
- Arista Security Advisory 0199 - VeloCloud Orchestrator SQL Injection Zero-Day (CVE-2026-114625)https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199Verified
- Arista Security Advisory 0183 - VeloCloud Orchestrator CVSS 10.0 RCE (CVE-2026-93952)https://www.arista.com/en/support/advisories-notices/security-advisory/24765-security-advisory-0183Verified
- New CVSS 10.0 VeloCloud Orchestrator Vulnerability Exploited in the Wildhttps://thehackernews.com/2026/09/new-cvss-100-velocloud-orchestrator.htmlVerified
- Attackers Exploit Arista VeloCloud Orchestrator Zero-Day in July 2026https://thehackernews.com/2026/07/attackers-exploit-arista-velocloud.htmlVerified
- Arista VeloCloud SD-WAN Operator Guide - Overview of VeloCloud Edge and Cloud Orchestratorhttps://www.arista.com/operator-guide-vc-6-4/sd-wan-6-4-overview-of-velocloud-edge-cloud-orchestratorVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant here because the attacker's ability to reach the VeloCloud Orchestrator from public IPs, escalate within a flat management plane, and pivot freely to downstream Edge devices reflects the absence of identity-aware segmentation and controlled access paths. By enforcing network-layer segmentation and restricting reachability to the orchestrator and its connected infrastructure, CNSF would likely reduce the attacker's operational reach and limit the blast radius across managed customer tenants.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Network-layer access to the orchestrator management interface from untrusted external source IPs would likely be constrained, reducing the reachability of attacker-controlled endpoints to the vulnerable SQL injection entry point and narrowing the exploitable attack surface.
Control: Zero Trust Segmentation
Mitigation: Even following a successful application-layer privilege escalation, Zero Trust segmentation would likely constrain what the newly elevated attacker identity could reach within the environment, reducing the scope of network resources accessible from the compromised orchestrator host.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement would likely reduce the attacker's ability to move freely between the orchestrator segment and Edge device segments or connected cloud workloads, constraining lateral reachability even when the attacker holds valid operator credentials within the management plane.
Control: Multicloud Visibility & Control
Mitigation: Centralized multicloud visibility over east-west and north-south traffic flows originating from the orchestrator workload would likely surface anomalous outbound connection attempts earlier, and policy enforcement at the fabric level could constrain unauthorized outbound paths used for C2 beaconing.
Control: Egress Security & Policy Enforcement
Mitigation: Egress policy enforcement would likely constrain the outbound data paths available to the attacker, reducing the volume and variety of data that could be transferred from the orchestrator environment to external attacker-controlled destinations without triggering policy violations.
If prior CNSF controls meaningfully constrained lateral movement and egress paths, the attacker's ability to reach all managed Edge devices and execute tenant-wide disruption would likely be reduced, limiting the realized blast radius to segments where the attacker maintained persistent reachability rather than the full orchestrator-managed tenant population.
Impact at a Glance
Affected Business Functions
- SD-WAN Network Orchestration and Policy Management
- Enterprise Branch Connectivity and Traffic Routing
- Customer and Partner Network Configuration Administration
- VeloCloud Edge Device Fleet Management
Estimated downtime: 7 days
Estimated loss: N/A
Full compromise of VeloCloud Orchestrator exposes all managed SD-WAN configuration data including network topology, routing policies, VPN credentials, customer and partner account credentials, and administrative audit logs. Attackers acting as local superusers may exfiltrate proprietary enterprise network architecture details, modify routing policies to redirect or intercept traffic, plant persistent backdoors or webshells on the VCO host, and potentially pivot to connected VeloCloud Edge devices across all managed customer networks. The breadth of exposure spans all tenants managed by a compromised orchestrator, making this a multi-tenant supply-chain style risk for managed service providers and enterprises relying on VeloCloud SD-WAN infrastructure.
Recommended Actions
Key Takeaways & Next Steps
- • Apply CNSF Cloud Firewall (ACF) and Egress Security controls immediately to restrict inbound access to the VCO web interface to trusted administrative networks only and block outbound connections from VCO hosts to unauthorized destinations, directly addressing Arista's interim mitigation guidance and limiting attacker C2 and exfiltration channels.
- • Deploy Inline IPS (Suricata) with updated signatures for CVE-2026-114625 SQL injection patterns to detect and block exploitation attempts against VCO web interfaces, including requests with unusual URL path components, encoded characters, and high-rate automated probing from known attacker IPs.
- • Enforce Zero Trust Segmentation to isolate the VeloCloud Orchestrator from general network access, applying least-privilege identity-based policies so that only explicitly authorized administrative identities and source networks can reach the VCO management plane, preventing low-privilege account abuse.
- • Enable Multicloud Visibility and Threat Detection controls (ThreatIQ/ThreatGuard) to baseline normal VCO traffic patterns and alert on anomalous interactions such as repeated malformed requests, connections from flagged IPs (74.82.197[.]86, 38.54.50[.]151), unexpected outbound activity, or unusual administrator actions indicative of post-exploitation behavior.
- • Activate Encrypted Traffic (HPE) protections using MACsec or IPsec for all data-in-transit between VCO, Edge devices, and managed infrastructure to prevent interception of SD-WAN configuration and customer data during and after orchestrator compromise, and implement East-West Traffic Security controls to contain lateral movement from a compromised VCO host toward Edge devices and customer network segments.



