Skip to main content
Mallory
CriticalExploited in the wildCISA KEVVulnerability

CVE-2026-93952: Improper Input Validation in Arista VeloCloud Orchestrator

Published Sep 22, 2026 · Updated 25 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 4 in a dayToday
CVSS9.5Critical · v4
EPSS1.4%73rd percentile
CISA KEVYesAdded Sep 22, 2026
In the wildActivePer CISA KEV
Vendor
Arista Networks
IdentifiersCVE-2026-93952CWE-20 · Improper Input Validation

CVE-2026-93952 is a critical improper-input-validation vulnerability in Arista VeloCloud Orchestrator (VCO) On-Prem. When certificate-based authentication between VeloCloud Edge and VCO is configured, a remote attacker with access to the VCO web interface and the public portion of an Edge authentication certificate can access privileged internal functionality without tenant or operator credentials. Successful exploitation may compromise the VCO host and the confidentiality, integrity, and availability of orchestrator-managed data. The vulnerability is actively exploited and has CVSS v3.1 and v4.0 scores of 10.0 and 9.5, respectively.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can compromise the orchestrator and its managed data, potentially exposing configuration data, device inventories, database contents, credentials, certificates, and key material. Unauthorized privileged functionality may enable configuration changes, command execution, data extraction, and service disruption. Compromise of the centralized orchestrator may also provide access to managed VeloCloud Edge devices, extending the impact across the SD-WAN deployment.

Mitigation

If you can’t patch tonight, do this now.

Restrict VCO web-interface access to trusted administrative networks until a fixed release is deployed; this reduces exposure but does not replace patching. Monitor inbound requests for unusual encoded components, internal-service references, and high request rates. Investigate unexpected outbound activity, unauthorized administrative or configuration changes, anomalous command execution, backdoor daemons, and webshells. Review web-access, backend-application, system, and database logs, and preserve evidence before remediation when compromise is suspected.

Remediation

Patch, then assume compromise.

Upgrade affected VCO 5.2 deployments to version 5.2.3.16 or a later fixed release in the 5.2.3 train, and affected VCO 6.4 deployments to version 6.4.2.8 or a later fixed release in the 6.4.2 train. Fixed releases for the affected 6.1 and 7.0 trains are not identified in the available vulnerability-specific information; consult Arista Security Advisory 0183 or Arista TAC for current upgrade guidance. Do not assume that a release fixing another VCO vulnerability also fixes CVE-2026-93952. Hosted and Dedicated VCO deployments have already been patched. If compromise is suspected, preserve relevant logs and filesystem timestamps where feasible, contact Arista TAC, rotate credentials, validate managed Edge devices, and restore or rebuild affected orchestrators from trusted sources as appropriate.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Arista NetworksVelocloud Orchestratorapplication
FAQ

Frequently asked questions

Is CVE-2026-93952 exploited in the wild?
Yes. As of Oct 23, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 22, 2026.
Is there a public exploit for CVE-2026-93952?
As of Oct 23, 2026, Mallory has found no public exploit for CVE-2026-93952.
Is there a patch for CVE-2026-93952?
Upgrade affected VCO 5.2 deployments to version 5.2.3.16 or a later fixed release in the 5.2.3 train, and affected VCO 6.4 deployments to version 6.4.2.8 or a later fixed release in the 6.4.2 train. Fixed releases for the affected 6.1 and 7.0 trains are not identified in the available vulnerability-specific information; consult Arista Security Advisory 0183 or Arista TAC for current upgrade guidance.
What products are affected by CVE-2026-93952?
Arista Networks Velocloud Orchestrator.
How severe is CVE-2026-93952?
CVE-2026-93952 has a CVSS v4 score of 9.5 (Critical) and an EPSS score of 1.4% (73rd percentile) as of Oct 23, 2026.
Activity feed

Recent activity

91 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
security weekNews · Oct 23, 2026Attackers Exploit Third VeloCloud Orchestrator Zero-Day in Four Months - SecurityWeekA previously exploited zero-day vulnerability in VeloCloud Orchestrator, patched by Arista in September 2026. It is mentioned as historical context; the article does not describe its technical mechanism or affected versions.Read more ↗malware newsNews · Oct 23, 2026CVE-2026-114625: Actively Exploited VeloCloud Orchestrator Flaw Grants Superuser Access - Malware News - Malware Analysis, News and IndicatorsAn earlier actively exploited VeloCloud Orchestrator vulnerability cited as background. Updates addressing this flaw do not necessarily protect against CVE-2026-114625. Its technical mechanism and specific fixed versions are not provided.Read more ↗socradar blogNews · Oct 23, 2026CVE-2026-114625: VeloCloud Orchestrator Flaw ExploitedAn earlier actively exploited VeloCloud Orchestrator vulnerability mentioned as background. Updates addressing this flaw do not necessarily protect against CVE-2026-114625. The content does not describe its underlying technical mechanism.Read more ↗the hacker newsNews · Oct 22, 2026Arista Warns of Critical VeloCloud SQL Injection Zero-Day Exploited in AttacksPreviously exploited VeloCloud Orchestrator vulnerability reported in September that did not require authentication. Listed fixes are 5.2.3.16 and 6.4.2.8. The advisory lists 6.1 releases through 6.1.3.7 as affected without identifying a fixed release; the article explicitly notes uncertainty over whether 6.1.3.10 also fixes this flaw. September's fixed releases remain vulnerable to CVE-2026-114625. Arista previously warned that orchestrator compromise could enable access to VeloCloud Edge devices.Read more ↗
+13 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity68Community discussion across Reddit, Mastodon, and other social sources.