NewsStocksArista Patches Third Actively Exploited VeloCloud Flaw in Three Months

Arista Patches Third Actively Exploited VeloCloud Flaw in Three Months

Author: Cryptopolitan·

Key Takeaways

  • •CVE-2026-114625 is an SQL-injection flaw rated 9.9 out of 10 under CVSS v3.1 that allowed Enterprise Read Only accounts to be elevated to superuser control of VeloCloud Orchestrator.
  • •Arista released fixed builds 5.2.3.18, 6.1.3.10, and 6.4.2.12 for affected 5.2.x, 6.1.x, and 6.4.x on-premises releases, while Hosted and Dedicated deployments were already patched.
  • •Arista confirmed the zero-day was exploited in the wild before a fix existed, with both attacks originating from the source IP addresses 74.82.197.86 and 38.54.50.151.
  • •The SQL injection is the third actively exploited VeloCloud Orchestrator flaw in three months, following a command-injection vulnerability disclosed on July 27, 2026, and another flaw revealed on September 22, 2026.
  • •Because VeloCloud Orchestrator centrally manages network connections across multiple sites, a breach could compromise several networks simultaneously, a risk that grows as Dell'Oro Group forecasts 14% annual SD-WAN revenue growth through 2030.
Arista Patches Third Actively Exploited VeloCloud Flaw in Three Months

Arista Networks patched an actively exploited zero-day vulnerability in its VeloCloud Orchestrator on October 22, 2026, closing a flaw that let attackers with the platform's lowest level of access seize control of the system used to manage network connections across multiple sites. The zero-day label reflects that the flaw was under attack before a fix existed. Arista acquired the VeloCloud platform from Broadcom in 2025.

From read-only account to superuser

Arista detailed the vulnerability in security advisory 0199, which identifies it as CVE-2026-114625, an SQL-injection flaw — a long-standing attack class in which crafted input manipulates database queries — rated 9.9 out of 10 under CVSS v3.1. The danger lies in how much control an attacker can gain from the lowest privilege tier.
Exploitation requires access to the web interface and valid login credentials. Once logged in, an attacker can leverage the SQL injection to elevate an Enterprise Read Only account — the platform's lowest-privilege role — to operator privileges and impersonate a superuser. In practice, a read-only account can be turned into full control of the platform. Arista confirmed that attackers have already exploited the vulnerability in the wild.

Patches and a forensic checklist

Operators of on-premises deployments should verify their software versions. Affected releases in the 5.2.x, 6.1.x, and 6.4.x trains require fixed builds 5.2.3.18, 6.1.3.10, and 6.4.2.12 respectively, or later releases in those trains. Hosted and Dedicated deployments, which run on Arista-operated infrastructure, have already been patched. On-premises deployments that have not yet moved to the fixed builds remain exposed in the meantime.

According to Arista, both attacks originated from two source IP addresses: 74.82.197.86 and 38.54.50.151. The company advises system administrators to investigate suspicious web requests, unexpected outbound connections, and unusual administrator activity. It also recommends limiting management access to trusted networks and preserving relevant logs in the event of a suspected breach.

The third VeloCloud flaw since summer

The SQL injection marks the third actively exploited flaw reported in VeloCloud Orchestrator within three months. Arista's advisory 0144, first issued on July 27, 2026, covered a command-injection vulnerability, while another flaw was disclosed on September 22 through advisory 0183. Both involved attack methods distinct from the latest vulnerability, but all three affected the same central management platform.

Because VeloCloud Orchestrator manages connections across multiple sites, a breach of the platform could compromise several networks simultaneously.

Patches arrive after the exploits

Industry data reflects the pattern of exploitation outpacing remediation. Verizon's 2026 Data Breach Investigations Report found that vulnerability exploitation accounted for 31% of data breaches, overtaking stolen credentials as the leading method attackers use to gain access to networks. The results underscore the need for businesses to fix vulnerabilities before attackers can leverage them.

In practice, businesses frequently cannot do so. Google's M-Trends 2026 report found that attackers exploit system vulnerabilities for an average of seven days before a fix becomes available. The report also highlighted threats against network devices such as VPNs and routers, which lack standard endpoint monitoring.

AI could sharpen the risk. In a separate investigation, Google researchers documented attackers using AI to plan and execute a large-scale credential-harvesting campaign in under six hours, an operation that compromised thousands of third-party credentials. There is no confirmed evidence that AI played a role in the VeloCloud attacks, but Google's findings show how AI-assisted operations can help attackers move faster and potentially cause greater damage before security teams can respond.

Why successive fixes matter for a growing market

Cyberattacks can carry severe financial consequences. IBM's 2026 study estimated the average global cost of a data breach at $4.99 million. Concerns about emerging threats are also mounting: the World Economic Forum found that 87% of respondents considered AI-related vulnerabilities the fastest-growing cyber risk during 2025.

The potential impact could grow as more businesses adopt SD-WANs — software-defined wide-area networks that connect multiple offices and allow companies to manage network traffic centrally. Dell'Oro Group forecasts 14% annual SD-WAN revenue growth through 2030. As these networks expand, a compromised central controller could disrupt business operations across multiple locations, potentially affecting companies in different countries.

Financial markets face similar concerns about operational disruption. Cryptopolitan previously reported attempted cyberattacks against major hedge funds, raising questions about possible spillover into crypto markets. Those incidents were separate from the VeloCloud attacks, but they highlight the importance of protecting critical systems.

For businesses running VeloCloud, the priorities are applying the available patches, checking for signs of earlier compromise, and securing the systems that connect their branch networks.