CVE Details

CVE-2026-16812 Arista VeloCloud Orchestrator On-Prem OS Command Injection Vulnerability
Published: 2026-07-27 CVSS: 10 CRITICAL Product: Arista VeloCloud Orchestrator Due Date: 2026-07-30

Arista VeloCloud Orchestrator On-Prem contains an OS command injection vulnerability that 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.

GitHub PoC

Warning: GitHub PoC repositories are unverified. Some may be fake or contain malware. Use caution and review code before running anything.

No GitHub PoC data.

FIRST EPSS

EPSS estimates the probability of exploitation in the next 30 days. Higher values indicate higher likelihood of real-world exploitation.

No EPSS data.

Timeline

CVE Stalker KEV MITRE GitHub FIRST (EPSS)

MITRE

CVSS

  • Score: 10
  • Severity: CRITICAL
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

SSVC

  • Exploitation: active
  • Automatable: yes
  • Technical Impact: total

References

Show Raw Data
Key Remaining Key Value
dataType CVE_RECORD
dataVersion 5.2
cveMetadata > cveId CVE-2026-16812
cveMetadata > assignerOrgId c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7
cveMetadata > state PUBLISHED
cveMetadata > assignerShortName Arista
cveMetadata > dateReserved 2026-07-23T21:46:32.558Z
cveMetadata > datePublished 2026-07-27T16:11:00.968Z
cveMetadata > dateUpdated 2026-07-27T19:50:04.023Z
containers > cna > providerMetadata > orgId c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7
containers > cna > providerMetadata > shortName Arista
containers > cna > providerMetadata > dateUpdated 2026-07-27T16:11:00.968Z
containers > cna > title VeloCloud Orchestrator OS Command Injection
containers > cna > datePublic 2026-07-27T16:07:00.000Z
containers > cna > problemTypes > 0 > descriptions > 0 > lang en
containers > cna > problemTypes > 0 > descriptions > 0 > cweId CWE-78
containers > cna > problemTypes > 0 > descriptions > 0 > description CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
containers > cna > problemTypes > 0 > descriptions > 0 > type CWE
containers > cna > impacts > 0 > capecId CAPEC-88
containers > cna > impacts > 0 > descriptions > 0 > lang en
containers > cna > impacts > 0 > descriptions > 0 > value CAPEC-88: OS Command Injection
containers > cna > affected > 0 > vendor Arista Networks
containers > cna > affected > 0 > product VeloCloud Orchestrator On-Prem
containers > cna > affected > 0 > versions > 0 > status affected
containers > cna > affected > 0 > versions > 0 > version 5.2.0
containers > cna > affected > 0 > versions > 0 > lessThan 5.2.3.14
containers > cna > affected > 0 > versions > 0 > versionType custom
containers > cna > affected > 0 > versions > 1 > status affected
containers > cna > affected > 0 > versions > 1 > version 6.1.0
containers > cna > affected > 0 > versions > 1 > lessThan 6.1.3.4
containers > cna > affected > 0 > versions > 1 > versionType custom
containers > cna > affected > 0 > versions > 2 > status affected
containers > cna > affected > 0 > versions > 2 > version 6.4.0
containers > cna > affected > 0 > versions > 2 > lessThan 6.4.2.4
containers > cna > affected > 0 > versions > 2 > versionType custom
containers > cna > affected > 0 > versions > 3 > status affected
containers > cna > affected > 0 > versions > 3 > version 7.0.0
containers > cna > affected > 0 > versions > 3 > lessThan 7.0.0.1
containers > cna > affected > 0 > versions > 3 > versionType custom
containers > cna > affected > 0 > defaultStatus unaffected
containers > cna > descriptions > 0 > lang en
containers > cna > descriptions > 0 > value 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. This functionality was intended to be for internal use only and is not intended to be remotely accessible. Hosted and Dedicated versions of VCO have already been patched in advance of this notice going out. This issue was discovered externally and is known to be actively exploited.
containers > cna > descriptions > 0 > supportingMedia > 0 > type text/html
containers > cna > descriptions > 0 > supportingMedia > 0 > base64 False
containers > cna > descriptions > 0 > supportingMedia > 0 > value <p>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.</p> <p>This functionality was intended to be for internal use only and is not intended to be remotely accessible.</p> <p>Hosted and Dedicated versions of VCO have already been patched in advance of this notice going out.</p> <p>This issue was discovered externally and is known to be actively exploited.</p>
containers > cna > references > 0 > url https://www.arista.com/en/support/advisories-notices/security-advisory/24364-security-advisory-0144
containers > cna > references > 0 > name Security Advisory 0144
containers > cna > references > 0 > tags > 0 vendor-advisory
containers > cna > configurations > 0 > lang en
containers > cna > configurations > 0 > value VCO is exposed by default. There is no configuration that can prevent the exposure. A successful attack requires network access to the VCO web interface. VCO tenant or operator credentials are not required for this exposure. Deployments that restrict VCO web interface access to trusted administrative networks can reduce risk of exposure.
containers > cna > configurations > 0 > supportingMedia > 0 > type text/html
containers > cna > configurations > 0 > supportingMedia > 0 > base64 False
containers > cna > configurations > 0 > supportingMedia > 0 > value <p>VCO is exposed by default. There is no configuration that can prevent the exposure. A successful attack requires network access to the VCO web interface. VCO tenant or operator credentials are not required for this exposure.</p> <p>Deployments that restrict VCO web interface access to trusted administrative networks can reduce risk of exposure.</p>
containers > cna > workarounds > 0 > lang en
containers > cna > workarounds > 0 > value The recommended resolution is to upgrade to a fixed VCO release as soon as it is available. For VCOs which are not on a supported release train, customers can contact TAC to discuss possible upgrade options for your release. 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. * Review recent administrator activity for unexpected changes.
containers > cna > workarounds > 0 > supportingMedia > 0 > type text/html
containers > cna > workarounds > 0 > supportingMedia > 0 > base64 False
containers > cna > workarounds > 0 > supportingMedia > 0 > value <p>The recommended resolution is to upgrade to a fixed VCO release as soon as it is available. For VCOs which are not on a supported release train, customers can contact TAC to discuss possible upgrade options for your release.</p> <p>Until the fixed software is deployed, operators should apply defense-in-depth controls appropriate for their environment:</p> <ul> <li>Restrict access to the VCO web interface to trusted administrative networks.</li> <li>Monitor the VCO for accesses from known malicious source IPs.</li> <li>Monitor for unexpected outbound network activity from the VCO host.</li> <li>Review recent administrator activity for unexpected changes.</li> </ul>
containers > cna > solutions > 0 > lang en
containers > cna > solutions > 0 > value The recommended resolution is to upgrade to a fixed VCO release at your earliest convenience. This vulnerability has been fixed in the following releases:   * VCO 5.2.3.14 and later in the 5.2 train * VCO 6.1.3.4 and later in the 6.1 train * VCO 6.4.2.4 and later in the 6.4 train
containers > cna > solutions > 0 > supportingMedia > 0 > type text/html
containers > cna > solutions > 0 > supportingMedia > 0 > base64 False
containers > cna > solutions > 0 > supportingMedia > 0 > value <p>The recommended resolution is to upgrade to a fixed VCO release at your earliest convenience.</p><div>This vulnerability has been fixed in the following releases:</div><div>&nbsp;</div><ul><li>VCO&nbsp;<b>5.2.3.14</b>&nbsp;and later in the 5.2 train</li><li>VCO&nbsp;<b>6.1.3.4</b>&nbsp;and later in the 6.1 train</li><li>VCO&nbsp;<b>6.4.2.4</b>&nbsp;and later in the 6.4 train</li></ul>
containers > cna > source > defect > 0 BUG 1901675
containers > cna > source > advisory 144
containers > cna > source > discovery EXTERNAL
containers > cna > x_generator > engine Vulnogram 1.0.4
containers > cna > metrics > 0 > format CVSS
containers > cna > metrics > 0 > scenarios > 0 > lang en
containers > cna > metrics > 0 > scenarios > 0 > value GENERAL
containers > cna > metrics > 0 > cvssV3_1 > version 3.1
containers > cna > metrics > 0 > cvssV3_1 > attackVector NETWORK
containers > cna > metrics > 0 > cvssV3_1 > attackComplexity LOW
containers > cna > metrics > 0 > cvssV3_1 > privilegesRequired NONE
containers > cna > metrics > 0 > cvssV3_1 > userInteraction NONE
containers > cna > metrics > 0 > cvssV3_1 > scope CHANGED
containers > cna > metrics > 0 > cvssV3_1 > confidentialityImpact HIGH
containers > cna > metrics > 0 > cvssV3_1 > integrityImpact HIGH
containers > cna > metrics > 0 > cvssV3_1 > availabilityImpact HIGH
containers > cna > metrics > 0 > cvssV3_1 > baseSeverity CRITICAL
containers > cna > metrics > 0 > cvssV3_1 > baseScore 10
containers > cna > metrics > 0 > cvssV3_1 > vectorString CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
containers > cna > metrics > 1 > format CVSS
containers > cna > metrics > 1 > scenarios > 0 > lang en
containers > cna > metrics > 1 > scenarios > 0 > value GENERAL
containers > cna > metrics > 1 > cvssV4_0 > attackVector NETWORK
containers > cna > metrics > 1 > cvssV4_0 > attackComplexity LOW
containers > cna > metrics > 1 > cvssV4_0 > attackRequirements NONE
containers > cna > metrics > 1 > cvssV4_0 > privilegesRequired NONE
containers > cna > metrics > 1 > cvssV4_0 > userInteraction NONE
containers > cna > metrics > 1 > cvssV4_0 > vulnConfidentialityImpact HIGH
containers > cna > metrics > 1 > cvssV4_0 > subConfidentialityImpact HIGH
containers > cna > metrics > 1 > cvssV4_0 > vulnIntegrityImpact HIGH
containers > cna > metrics > 1 > cvssV4_0 > subIntegrityImpact HIGH
containers > cna > metrics > 1 > cvssV4_0 > vulnAvailabilityImpact HIGH
containers > cna > metrics > 1 > cvssV4_0 > subAvailabilityImpact HIGH
containers > cna > metrics > 1 > cvssV4_0 > exploitMaturity NOT_DEFINED
containers > cna > metrics > 1 > cvssV4_0 > Safety PRESENT
containers > cna > metrics > 1 > cvssV4_0 > Automatable NOT_DEFINED
containers > cna > metrics > 1 > cvssV4_0 > Recovery NOT_DEFINED
containers > cna > metrics > 1 > cvssV4_0 > valueDensity NOT_DEFINED
containers > cna > metrics > 1 > cvssV4_0 > vulnerabilityResponseEffort NOT_DEFINED
containers > cna > metrics > 1 > cvssV4_0 > providerUrgency NOT_DEFINED
containers > cna > metrics > 1 > cvssV4_0 > version 4.0
containers > cna > metrics > 1 > cvssV4_0 > baseSeverity CRITICAL
containers > cna > metrics > 1 > cvssV4_0 > baseScore 10
containers > cna > metrics > 1 > cvssV4_0 > vectorString CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:P
containers > adp > 0 > metrics > 0 > other > type ssvc
containers > adp > 0 > metrics > 0 > other > content > id CVE-2026-16812
containers > adp > 0 > metrics > 0 > other > content > role CISA Coordinator
containers > adp > 0 > metrics > 0 > other > content > options > 0 > Exploitation active
containers > adp > 0 > metrics > 0 > other > content > options > 1 > Automatable yes
containers > adp > 0 > metrics > 0 > other > content > options > 2 > Technical Impact total
containers > adp > 0 > metrics > 0 > other > content > version 2.0.3
containers > adp > 0 > metrics > 0 > other > content > timestamp 2026-07-27T19:45:04.589433Z
containers > adp > 0 > metrics > 1 > other > type kev
containers > adp > 0 > metrics > 1 > other > content > dateAdded 2026-07-27
containers > adp > 0 > metrics > 1 > other > content > reference https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-16812
containers > adp > 0 > references > 0 > url https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-16812
containers > adp > 0 > references > 0 > tags > 0 government-resource
containers > adp > 0 > title CISA ADP Vulnrichment
containers > adp > 0 > providerMetadata > orgId 134c704f-9b21-4f2e-91b3-4a467353bcc0
containers > adp > 0 > providerMetadata > shortName CISA-ADP
containers > adp > 0 > providerMetadata > dateUpdated 2026-07-27T19:50:04.023Z