Arista Warns of Critical VeloCloud SQL Injection Zero-Day Exploited in Attacks
Arista warns of critical VeloCloud SQL injection zero-day exploited in attacks.
Arista has issued a warning about a critical zero-day SQL injection vulnerability affecting its VeloCloud Orchestrator (VCO). Attackers are actively exploiting this flaw to gain operator privileges within the SD-WAN management system, even with low-level customer accounts. The vulnerability allows unauthorized access and control over the VeloCloud networks.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Arista?
Get an email when a new story names Arista, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonA critical SQL injection zero-day in Arista's VeloCloud Orchestrator allowed attackers to escalate from low-privilege customer accounts to operator-level access within a widely deployed SD-WAN management system. SQL injection remains one of the most well-understood and preventable vulnerability classes, yet its presence here as a zero-day in enterprise network infrastructure demonstrates failures in secure coding practices and pre-release security testing. The active exploitation of this flaw means organizations relying on VeloCloud for network management face real-time risk of unauthorized control over their SD-WAN environments. This matters because SD-WAN orchestrators sit at the heart of enterprise network operations — compromise grants attackers significant lateral movement opportunities across distributed infrastructure.
What helps against this
How we list vendors- Privileged access management (PAM)
Admin accounts stop being one stolen password away from control of everything.
- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
Indicators of Compromise
Addresses and file hashes are copied from the publisher's page by pattern matching. Names are picked by AI. On stories from before 17 November 2026, some addresses and hashes were picked by AI too. Not reviewed by an editor. How this works
- ip: 38.54.50.151
- ip: 74.82.197.86