Third VeloCloud Orchestrator Flaw Exploited in 2026: CVE-2026-114625 in a Pattern
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…
Arisota has reported three critical vulnerabilities in VeloCloud Orchestrator since late July 2026, all of which have been exploited. The latest, CVE-2026-114625, is an SQL injection flaw that allows any authenticated user, including low-level customer roles, to escalate to a superuser operator. This marks the third time the same management plane has produced critical flaws with delayed operational responses.
The earlier vulnerabilities CVE-2026-16812 and CVE-2026-93952 were both rated lower on the CVSS scale and did not require authentication. The consistency in advisory language across the three vulnerabilities suggests a stable understanding of the asset, not a stable cause. The fact that orchestrators patched for earlier vulnerabilities remain vulnerable to CVE-2026-114625 indicates patch compounding.
Arista states that hosted and dedicated orchestrators have been patched, but on-premises customers must apply specific fixes themselves. To improve security, organisations should shorten the interval between advisories and build verification, and treat the orchestrator's management interface as internet-exposed by default.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.