How to fix CVE-2026-114625: Arista VeloCloud Orchestrator (exploited in the wild)

VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator. On an affected system, any authenticated user can gain operator privileges and masquerade as a local "superuser operator" user. This includes access to functionality that is intended for internal use only and which is not intended to be remotely accessible. Hosted, including Dedicated, versions of VCO were impacted and have already been patched.

• Severity: CRITICAL (CVSS 4.0 9.4, vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H).
• Weakness: CWE-89.
• NVD published 2026-10-22, status Analyzed.

Anyone running Arista VeloCloud Orchestrator in the version ranges below. Internet-facing instances are the priority.

• arista velocloud orchestrator: from 5.2.0 up to (not including) 5.2.3.18.
• arista velocloud orchestrator: from 6.1.0 up to (not including) 6.1.3.10.
• arista velocloud orchestrator: from 6.4.0 up to (not including) 6.4.2.12.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

• Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-10-23; federal remediation due date 2026-10-26.

• EPSS (probability of exploitation activity in the next 30 days): 0.81%, higher than 57% of all scored CVEs (as of 2026-10-24).
• CVERadar threat level: 62/100 (see methodology).
• Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1005 Data from Local System (inferred).

1. Find every instance. List where Arista VeloCloud Orchestrator runs, including test, DR and forgotten internet-facing systems, and record the installed version.
2. Upgrade to a fixed release. arista velocloud orchestrator: 5.2.3.18 or later; arista velocloud orchestrator: 6.1.3.10 or later; arista velocloud orchestrator: 6.4.2.12 or later. Get the build from the vendor advisory.
3. If you can't patch today, follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build (5.2.3.18 or later). Re-scan from outside if the service is exposed.
5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

• T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to VeloCloud Orchestrator (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-10-22.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

• NVD: CVE-2026-114625 nvd.nist.gov/vuln/detail/CVE-2026-114625
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-114625
• Vendor link from CISA KEV www.arista.com/en/support/advisories-notices/security-advisory/24838-s
• CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST EPSS (2026-10-24) api.first.org/data/v1/epss?cve=CVE-2026-114625