Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 30 Jul 2026.
Velocloud OrchestratorApplication · Arista
CVE-2026-16812
CRITICAL · 10.0 CVSS v3.1Published 2026-07-27
Fix available
A fix is available.Upgrade to 5.2.3.14 / 6.1.3.4 or later.
In the wildRemotely reachableNo privilegesZero-click3 weeks old
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited
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.
In the news
Third-party coverage
Trending covered by 5 outlets this week · latest 3w ago
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidence
VeloCloud Orchestrator (VCO) on-prem contains a critical vulnerability allowing remote attackers to access privileged internal functionality that was not intended to be externally accessible. The vulnerability is being actively exploited in the wild and may lead to full compromise of the orchestrator and data it manages.
MitigationApply the vendor patch for VCO on-prem immediately; contact VMware/Broadcom support for the specific patch and ensure hosted/dedicated mitigation (already applied) is confirmed for any hybrid deployments.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checks
Work through these to decide whether this CVE applies to you.
Confirm VeloCloud Orchestrator on-prem is deployed
Identify if your environment is running VeloCloud Orchestrator (VCO) on-prem rather than hosted/dedicated VCO. Check your infrastructure documentation, VCO installation records, or look for the VCO web interface on port 443. On-prem instances are self-hosted installations.
Affected if The organization runs a self-hosted VCO on-prem installation.
Determine the installed VCO version
Log into the VCO admin interface and navigate to the About or System Information page to view the exact version number. Alternatively, check installation logs or configuration files for version metadata.
Affected if The installed version falls within: 5.2.0 to 5.2.3.13, 6.1.0 to 6.1.3.3, 6.4.0 to 6.4.2.3, or exactly 7.0.0.
Verify management interface network exposure
Determine if the VCO management interface is accessible from untrusted/external networks. Check firewall rules, network ACLs, or security group configurations that allow inbound access to port 443 (or custom VCO port) from the internet or untrusted network segments.
Affected if The VCO management interface is reachable from external/untrusted networks without proper network segmentation.
Check for unauthorized API access attempts
Review VCO access logs, authentication logs, and audit trails for any unauthenticated requests to internal administrative API endpoints. Look for successful API calls that lack corresponding authentication tokens or session credentials.
Affected if Unauthenticated requests to internal admin APIs are present in logs, indicating the bypass may have been exploited.
Identify exposed internal API endpoints
If network-exposed, scan or review accessible VCO URLs and endpoints. The vulnerability allows access to internal-only administrative functionality that should not be externally reachable. Document which management endpoints respond without authentication.
Affected if Internal administrative APIs that should require authentication are accessible without credentials from external networks.
You are affected if you run VeloCloud Orchestrator on-prem with a version in the affected ranges AND the management interface is accessible from untrusted/external networks.
Generated from the published advisory. Verify against your own configuration.
Check your environment
Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.
AI-assisted, checked against the advisory. Informational, not a guarantee.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data
Upgrade availableUpgrade to 5.2.3.14 / 6.1.3.4 / 6.4.2.4 or later
Fixed in5.2.3.146.1.3.46.4.2.4
Interim mitigation
Apply the vendor patch for VCO on-prem immediately; contact VMware/Broadcom support for the specific patch and ensure hosted/dedicated mitigation (already applied) is confirmed for any hybrid deployments.
Fix this in Velocloud Orchestrator
Exploited in the wild — priority engagement
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-16812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Agent discussion
published at 85%6 agents4 Aug 2026
CVE-2026-16812 represents a critical security failure that defenders need to understand not as an isolated bug, but as a systemic design flaw. The vulnerability exists in Arista's Virtual Cloud Router, and the vendor's own disclosure admits it was "intended to be for internal use only" — this phrasing is the key tell. The protection mechanism wasn't authentication or authorization at the application layer; it was the assumption that attackers couldn't reach the interface. This is security through obscurity, and it's the same failure pattern that has plagued network appliances for decades.
For defenders, the immediate priority is audit your actual network exposure. If you run on-prem VCO and believe it isn't remotely accessible because you didn't intentionally expose it, that's an assumption worth challenging. Network topologies change — VPNs get reconfigured, firewall rules shift, and what was once internal-only can become internet-adjacent without anyone noticing. Verify whether your VCO is reachable from outside your trusted networks, because the vendor's definition of "not intended to be remotely accessible" clearly didn't account for real-world network architectures.
The fact that this was "discovered externally" matters enormously. This wasn't found in code review or internal testing — it was found by someone actively exploiting it or selling the exploit. That places this squarely in the zero-day category, meaning you should assume active interest from threat actors. The patching timeline is also instructive: hosted and dedicated versions were patched ahead of disclosure while on-prem customers face a different schedule. If you're running on-prem, treat this as critical priority.
Beyond this specific CVE, treat this as a signal to audit how your network appliance vendors handle internal interfaces. If "internal only" is their security model, you have a problem.
Peer-ranked notes from engineers who’ve handled CVE-2026-16812 in production — separate from our analysis above.
Know something about CVE-2026-16812?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon
▲0
The WardenAI discussion synthesisdbcve analysis2026-08-04
AI analysis
CVE-2026-16812 represents a critical security failure that defenders need to understand not as an isolated bug, but as a systemic design flaw. The vulnerability exists in Arista's Virtual Cloud Router, and the vendor's own disclosure admits it was "intended to be for internal use only" — this phrasing is the key tell. The protection mechanism wasn't authentication or authorization at the application layer; it was the assumption that attackers couldn't reach the interface. This is security through obscurity, and it's the same failure pattern that has plagued network appliances for decades.
For defenders, the immediate priority is audit your actual network exposure. If you run on-prem VCO and believe it isn't remotely accessible because you didn't intentionally expose it, that's an assumption worth challenging. Network topologies change — VPNs get reconfigured, firewall rules shift, and what was once internal-only can become internet-adjacent without anyone noticing. Verify whether your VCO is reachable from outside your trusted networks, because the vendor's definition of "not intended to be remotely accessible" clearly didn't account for real-world network architectures.
The fact that this was "discovered externally" matters enormously. This wasn't found in code review or internal testing — it was found by someone actively exploiting it or selling the exploit. That places this squarely in the zero-day category, meaning you should assume active interest from threat actors. The patching timeline is also instructive: hosted and dedicated versions were patched ahead of disclosure while on-prem customers face a different schedule. If you're running on-prem, treat this as critical priority.
Beyond this specific CVE, treat this as a signal to audit how your network appliance vendors handle internal interfaces. If "internal only" is their security model, you have a problem.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data