How severe is CVE-2026-16812?

CVE-2026-16812 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-16812 being actively exploited?

Yes. CVE-2026-16812 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-07-27, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2026-16812?

CVE-2026-16812 primarily affects Arista Velocloud Orchestrator. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-16812?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

When was CVE-2026-16812 published?

CVE-2026-16812 was published on 2026-07-27 and last updated on 2026-07-28.

CVE-2026-16812

CVE-2026-16812 is a critical-severity vulnerability in Arista Velocloud Orchestrator with a CVSS 3.x base score of 10.0. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2026-07-27). The underlying weakness is classified as CWE-78.

Key facts

Severity: Critical (CVSS 3.x base score 10.0)
CVSS v4: 10.0
EPSS exploit prediction: 1% (57th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2026-07-27)
Weakness: CWE-78
Affected product: Arista Velocloud Orchestrator
Published: 2026-07-27
Last modified: 2026-07-28

Description

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.

Frequently asked questions

What is CVE-2026-16812?: 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.
How severe is CVE-2026-16812?: CVE-2026-16812 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-16812 being actively exploited?: Yes. CVE-2026-16812 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-07-27, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2026-16812?: CVE-2026-16812 primarily affects Arista Velocloud Orchestrator. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-16812?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
When was CVE-2026-16812 published?: CVE-2026-16812 was published on 2026-07-27 and last updated on 2026-07-28.

References

Affected products (2)

cpe:2.3:a:arista:velocloud_orchestrator:*:*:*:*:*:*:*:*
cpe:2.3:a:arista:velocloud_orchestrator:7.0.0:*:*:*:*:*:*:*

More vulnerabilities in Arista Velocloud Orchestrator

CVE-2020-3973 — High (CVSS 8.8): The VeloCloud Orchestrator does not apply correct input validation which allows for blind SQL-injection. A malicious…
CVE-2026-31431 — High (CVSS 7.8): In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating…

All CVEs affecting Arista Velocloud Orchestrator →

Other CWE-78 (OS Command Injection) vulnerabilities

CVE-2026-19188 — Critical (CVSS 10.0): A critical OS command injection vulnerability has been identified in the Haiwell IoT Cloud HMI Gateway product. The…
CVE-2026-48362 — Critical (CVSS 10.0): ColdFusion is affected by an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')…
CVE-2026-6516 — Critical (CVSS 10.0): Zohocorp ManageEngine ADAudit Plus versions before 8606 are affected by Unauthenticated Remote code execution due to…
CVE-2026-46339 — Critical (CVSS 10.0): 9Router is an AI router & token saver. From 0.4.30 until 0.4.37, 9Router's src/proxy.js middleware did not protect…
CVE-2026-59726 — Critical (CVSS 10.0): Ruflo is an agent meta-harness for Claude Code and Codex. Prior to 3.16.3, ruflo's default docker-compose deployment…
CVE-2026-56004 — Critical (CVSS 10.0): A shellcode injection in the mercurial handler of the obs tar_scm source service before version 0.12.4 could be used by…

Browse all CWE-78 (OS Command Injection) vulnerabilities →