Skip to content
major vulnerability· requires attention

Enterprise SD‑WAN orchestrator (Arista VeloCloud) is widely deployed; SQLi leads to operator/superuser compromise and is listed in CISA KEV — broad, high-impact risk.

Networks

CVE-2026-114625

9.4
Critical
KEV · Exploited in wildEPSS 1%Patch availableOct 24, 2026

SQL injection in Arista VeloCloud Orchestrator lets authenticated users gain superuser/operator access.

common questions

Is CVE-2026-114625 being exploited?

Yes. CVE-2026-114625 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-114625?

CVE-2026-114625 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-114625?

Yes. A fix has been recorded for CVE-2026-114625. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-114625 affect?

CVE-2026-114625 affects Arista VeloCloud Orchestrator (on‑prem). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-114625?

Apply Arista advisory patch/mitigations immediately; isolate internet‑exposed VCO and follow CISA BOD 26‑04.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Arista VeloCloud Orchestrator (on‑prem)
impact

Authenticated SQLi enables operator/superuser impersonation, full orchestrator compromise: steal/modify configs, push malicious policies, disrupt service.

action required

Immediate action required

affected versions
Arista Networks VeloCloud Orchestrator
  • affected>= 5.2.0 and < 5.2.3.18
  • affected>= 6.1.0 and < 6.1.3.10
  • affected>= 6.4.0 and < 6.4.2.12

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved