PoC Monitor
← All CVEs
CVE-2026-114625published 22 Oct 2026 20:47 UTCData: JSON · API

Arista Networks VeloCloud Orchestrator

Security Advisory 0199

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.9critical · scored by CNA · CWE-89
CISA KEV 23 Oct 20261 day after publication

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Arista Networks VeloCloud Orchestrator
  • >= 5.2.0, < 5.2.3.18
  • >= 6.1.0, < 6.1.3.10
  • >= 6.4.0, < 6.4.2.12

Fixed in 5.2.3.18, 6.1.3.10, 6.4.2.12

Mitigation

The recommended resolution is to upgrade to a fixed VCO release at your earliest convenience. These vulnerabilities have been fixed in the following releases: - VCO 5.2.3.18 and later in the 5.2 train - VCO 6.1.3.10 and later in the 6.1 train - VCO 6.4.2.12 and later in the 6.4 train

Workaround

Until the fixed software is deployed, operators should apply defense-in-depth controls appropriate for their environment: - Restrict access to the VCO web interface to trusted administrative networks. - Monitor the VCO for accesses from known malicious source IPs. - Monitor for unexpected outbound network activity from the VCO host. - Consider blocking outbound ports not needed for normal activities. - Monitor for backdoor daemons and webshells. - Review recent administrator activity for unexpected changes.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published22 Oct 2026 · t = 0Added to CISA KEV23 Oct 2026 · t+1d

No public PoC found yet; added to CISA KEV 1 day after publication.

PoC repositories

Found on GitHub.

1 informational

Informational 1
RepositoryCreatedFound by usStarsAssessment
definitiveref/CVE-2026-114625-Proof-Of-Concept 30 Oct 2026 +7.7 d 14 Nov 2026 1 Informational · write-up

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.