Third VeloCloud Orchestrator Flaw Exploited in 2026: CVE-2026-114625 in a Pattern
CVE-2026-114625 is the third VeloCloud Orchestrator vulnerability that Arista has reported as exploited since late July 2026. The repetition is the story: the same management plane keeps producing critical, network-reachable flaws, and the operational response keeps arriving after exploitation has begun.
The sequence
In July 2026, CVE-2026-16812, an OS command injection, was reported exploited. In September 2026, CVE-2026-93952, an input validation flaw, followed. The current entry, CVE-2026-114625, is an SQL injection rated 9.9 on CVSS 3.1 and classified as CWE-89.
One difference matters. Neither earlier flaw required authentication. CVE-2026-114625 does, with any authenticated user including the lowest built-in customer role able to escalate to a local "superuser operator".
What the pattern suggests
The advisory language is nearly identical across the three: exploitation may compromise the confidentiality, integrity and availability of the orchestrator and the data it manages. That consistency implies a stable understanding of the asset, not a stable cause. Three different vulnerability classes in one product within a quarter is a signal about attack surface breadth, not about a single coding habit.
A second signal is patch compounding. Reporting notes that orchestrators carrying the fixes for the July and September flaws remain vulnerable to this one, because those builds sit below the new fixed releases on the same train. Each cycle invalidates the previous assurance claim.
The vendor position
Arista states that this flaw was detected by the company and is known to be actively exploited, and that hosted and dedicated orchestrators have already been patched. On-premises customers must apply 5.2.3.18, 6.1.3.10 or 6.4.2.12 themselves. VeloCloud Gateway and VeloCloud Edge are not affected.
What to change upstream
Two changes follow for organisations that treat VeloCloud Orchestrator as critical. First, shorten the interval between an advisory and a build verification, because a train-specific fixed version is easy to confuse with a general "we are patched" claim. Second, treat the orchestrator's management interface as internet-exposed by default and make reachability an explicit, reviewed exception.
Arista's own interim guidance, restricting the interface to trusted administrative networks, blocking unneeded outbound ports, watching for backdoor daemons and web shells, and reviewing administrator activity, reads like standing advice rather than a one-off.
Exposure context
A ZoomEye query for the VeloCloud title fingerprint returned 520 matching assets on 22 October 2026, a measure of visible product-family interfaces rather than confirmed vulnerable systems. It suggests the population that must track these quarterly advisories is not small.
References
- Arista Security Advisory 0199: https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199
- CVE.org record for CVE-2026-114625: https://cveawg.mitre.org/api/cve/CVE-2026-114625
- The Hacker News, covering the July and September 2026 flaws: https://thehackernews.com/2026/10/arista-warns-of-critical-velocloud-sql.html
- SecurityOnline analysis: https://securityonline.info/velocloud-orchestrator-cve-2026-114625-exploited/
