VeloCloud Orchestrator Zero-Day. Patch. Restrict. Hunt.
An actively exploited SQL injection in on-premises Arista VeloCloud Orchestrator lets any logged-in user, even with the lowest read-only role, gain superuser operator control. Clear steps for businesses, internal IT teams and MSPs running VeloCloud SD-WAN.
At a Glance
Facts from Arista Security Advisory 0199. Actively exploited per Arista. Not in the CISA KEV catalog or NVD as of 22 October 2026 (catalog of 21 October checked at 21:20 BST). Last updated 22 October 2026, 21:30 BST.
Actively exploited
Arista detected the flaw and says it is known to be actively exploited. Fixed releases are available for on-premises VCO.
CVSS 9.9
SQL injection (CWE-89). Any authenticated user, down to the Enterprise Read Only role, can gain operator privileges and act as a local superuser operator, and may impact the VCO host.
On-prem VCO
On-premises VeloCloud Orchestrator (formerly VMware SD-WAN by VeloCloud) before 5.2.3.18, 6.1.3.10 and 6.4.2.12. Hosted and Dedicated orchestrators are already patched. Gateways and Edges are not affected. Arista says releases not on its list are not vulnerable, so the 7.0 train is treated as not affected.
Multi-tenant
VCO holds operator, partner and customer accounts. One low-privilege customer login can lead to operator control of the whole orchestrator and the tenants it manages.
Two earlier VCO flaws are exploited. Orchestrators patched only for September's CVE-2026-93952 (5.2.3.16, 6.4.2.8) are below the new fixed versions and still vulnerable.
Arista publishes Security Advisory 0199: CVE-2026-114625, actively exploited, with fixed releases and two attacker IPs.
Not yet in the CISA KEV catalog or NVD.
Upgrade every on-prem VCO, restrict web access, preserve logs and hunt for compromise.
What to Do in the Next 24 Hours
Proactive on the left. Reactive on the right. Tick both tracks.
Patch and restrict
- Upgrade on-prem VCO to 5.2.3.18, 6.1.3.10 or 6.4.2.12 or later.
- Restrict the VCO web UI to trusted admin networks.
- Audit operator, partner and customer accounts.
- Block outbound ports the VCO does not need.
Hunt and preserve
- Block and search logs for 74.82.197[.]86 and 38.54.50[.]151.
- Review web logs for encoded or URL-like path segments and request spikes.
- Look for unexpected outbound traffic, webshells and unexplained admin changes.
- Preserve web, application, system and database logs before upgrading.
Proactive: Patch First, Then Reduce Exposure
Arista says VCO is exposed by default and no setting prevents the exposure. Upgrading is the fix.
Upgrade every on-prem VCO
Check the VCO version and upgrade to 5.2.3.18, 6.1.3.10 or 6.4.2.12 or later on your train. Orchestrators patched only for September's CVE-2026-93952 (5.2.3.16 or 6.4.2.8) are below these fixed versions and still vulnerable. On an unsupported release train, contact Arista TAC about upgrade options. If you suspect compromise, preserve logs first (see Reactive).
Restrict the web interface
Limit access to the VCO web UI to trusted administrative networks. Do not leave it open to the internet.
Audit accounts
Review every operator, partner and customer account. Remove ones that are not needed and check for accounts or role changes you cannot explain. Any valid login, even read-only, is enough to exploit this flaw.
Limit outbound traffic
Block outbound ports the VCO does not need for normal operation, and alert on unexpected outbound connections from the VCO host.
Free Checker Scripts
Built by the CybaVerse threat hunt team. Run it for every on-prem orchestrator you or your clients run to get a clear verdict and scan web logs for the published indicators.
check_vco.sh / Check-VCO.ps1
Compares the VCO version you pass in against the fixed releases in Arista Advisory 0199, and optionally scans exported VCO web access logs for the attacker IPs, URL-like or encoded path segments and request spikes. It does not read the version from the orchestrator itself, so pass it in.
./check_vco.sh --version 6.4.2.10 --log access.log --strict-logs
pwsh ./Check-VCO.ps1 -Version 6.4.2.10 -LogPath .\access.log -StrictLogsRead-only by design
Both scripts are read-only. They make no network calls, do no probing and change nothing. Upgrading and incident response stay with you. Review any script before you run it.
Verdicts
- PATCHEDVersion is at or above the fix on its train, or on a train treated as not affected (such as 7.0).
- LIKELY VULNERABLEVersion is below the fix, or log indicators were found with strict log mode. Upgrade and investigate.
- UNKNOWNVersion unreadable or end of support. Contact Arista TAC.
- ERRORThe check failed, so the result is unknown.
Exit codes
| Code | Meaning |
|---|---|
| 0 | PATCHED or not affected |
| 1 | LIKELY VULNERABLE |
| 2 | UNKNOWN |
| 3 | ERROR |
MSPs and internal IT teams can use the exit code in RMM or deployment tooling to flag hosts at scale.
Know the limits
- The checker needs the version passed in. It does not connect to the orchestrator.
- The KQL has not been run on a live tenant. Set your VCO hosts and validate field names first.
- A clean log scan does not rule out compromise. The attacker IPs are the only published indicators.
- Not in CISA KEV or NVD yet. Recheck as they update.
Reactive: How to Hunt
Treat an unpatched VCO with any sign of the activity below as compromised. CybaOps can run these hunts across your estate or your clients'.
Attacker IPs
Block the two IP addresses Arista published and search firewall, proxy and VCO web logs for them.
grep -E "74\.82\.197\.86|38\.54\.50\.151" /path/to/vco/web/access.log*Web access log patterns
Review VCO web access logs for requests with unusual URL-like path components, encoded characters, references to local or internal services, and spikes in request rate, especially from low-privilege accounts.
Host and admin activity
Look for unexpected outbound connections from the VCO host, backdoor daemons, webshells and administrator changes nobody can explain.
Preserve and respond
Before upgrading, where operationally feasible, preserve VCO web access, backend application, system and database logs and relevant file-system timestamps. If compromise is confirmed, treat the customer tenants and connected Edges managed by that orchestrator as exposed and run incident response.
Detection pack: KQL and Sigma
Hunts from the CybaVerse threat hunt team for Microsoft Sentinel and Defender XDR: the attacker IPs in both directions, web access anomalies, request spikes, new outbound connections from the VCO host and an admin-change starting point. Two Sigma rules cover the web and firewall views. Run them in CybaOps or your own SIEM.
The KQL has not been run on a live tenant. Set your VCO hosts and validate table and field names before relying on results.
KQL hunting queries (Sentinel and Defender XDR)
Loading queries. If they don't appear, download the full pack below. The .kql file is inside it.Sigma: VCO web access from attacker IPs or URL-like and encoded paths
title: VeloCloud Orchestrator Web Access From Arista-Published IOC IPs or URL-like/Encoded Path Segments (CVE-2026-114625)
id: 6f1d2c3a-8b4e-4f0a-9c71-2a5e0d114625
status: experimental
description: |
Hunts VCO nginx/web access logs for the two source IPs Arista published in Security Advisory 0199
and for generic anomalies Arista advises reviewing (URL-like path components, encoded slashes,
references to local services). Generic by design; contains no exploit payload. Untested in production.
references:
- https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199
author: Oliver Spence
date: 2026-10-22
tags:
- attack.initial-access
- attack.t1190
- cve.2026-114625
logsource:
category: webserver
detection:
sel_ioc:
c-ip:
- '74.82.197.86'
- '38.54.50.151'
sel_urllike:
cs-uri-stem|contains:
- 'http://'
- 'https://'
- 'http%3a'
- 'https%3a'
- '%2f%2f'
- 'localhost'
- '127.0.0.1'
- '0.0.0.0'
condition: sel_ioc or sel_urllike
fields:
- c-ip
- cs-method
- cs-uri-stem
- cs-uri-query
- sc-status
falsepositives:
- Legitimate redirect or callback parameters; scope this rule to VCO hosts only
level: highSigma: Network connection to or from attacker IPs
title: Network Connection To or From Arista-Published VeloCloud Orchestrator Attacker IPs (CVE-2026-114625)
id: 9a7c4e21-3d5b-4b8e-a1f6-7e0c2b114625
status: experimental
description: Connections involving IPs Arista observed conducting CVE-2026-114625 attacks (Security Advisory 0199).
references:
- https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199
author: Oliver Spence
date: 2026-10-22
tags:
- attack.initial-access
- attack.t1190
- cve.2026-114625
logsource:
category: firewall
detection:
sel_src:
src_ip:
- '74.82.197.86'
- '38.54.50.151'
sel_dst:
dst_ip:
- '74.82.197.86'
- '38.54.50.151'
condition: 1 of sel_*
falsepositives:
- None expected; IPs may be reassigned over time
level: highIndicators of compromise
Published by Arista. An IP match needs investigation in context. A clean search does not rule out compromise.
# From Arista Security Advisory 0199 (22 October 2026). Defanged.
# IP addresses observed conducting the attacks: block and search logs
74.82.197[.]86
38.54.50[.]151
# Web access log patterns to investigate (behavioural, not proof on their own)
- unusual URL-like path components
- encoded characters in the path
- references to local or internal services
- high request ratesVeloCloud Orchestrator FAQ
Short answers based on Arista's advisory as of 22 October 2026.
Which versions are affected?
On-premises VeloCloud Orchestrator 5.2.x before 5.2.3.18, 6.1.x before 6.1.3.10 and 6.4.x before 6.4.2.12. Arista has not assessed end-of-support releases.
Is it being exploited?
Yes. Arista says it is known to be actively exploited. It is not in the CISA KEV catalog or NVD as of 22 October 2026.
Are Edges, Gateways or hosted VCO affected?
VeloCloud Gateways and Edges are not affected. Hosted and Dedicated orchestrators were affected and Arista has already patched them. The 7.0 train is not named by Arista, and the advisory says unlisted releases are not vulnerable, so it is treated as not affected.
I patched for the July and September flaws. Am I safe?
No. Those fixed releases are older than the new fixes, so upgrade again.
Why does this matter for MSPs?
VCO is multi-tenant. Any customer user with the lowest read-only role can gain operator control of the orchestrator that manages every tenant.
Detect and Remediate VeloCloud Exposure Across Your Estate
CybaOps monitors your network infrastructure, servers and management platforms, whether that's your own business or your clients'. Our SOC runs these threat hunts, alerts on known attacker IPs and suspicious activity, and drives remediation through to a verified fix, so proactive checks and reactive response happen in one place.