VeloCloud Edge: Missing Authentication for Critical Functionality
CVE-2026-86106 is a critical-severity missing authentication for critical functionality vulnerability in VeloCloud Edge from Arista Networks, with a CVSS 3.1 base score of 9.6 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions 5.2.0.0, 5.2.7.0, 6.1.5.0 as the first without the flaw, so updating VeloCloud Edge to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update VeloCloud Edge to 5.2.0.0 or 5.2.7.0 or 6.1.5.0 or 6.4.2.0, whichever matches your release line, or a later version.
- Read the advisory on arista.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Arista Networks | VeloCloud Edge | 1.0.0.0 up to, but not including, 5.2.0.0; 5.2.0.0 up to, but not including, 5.2.7.0; 6.1.0.0 up to, but not including, 6.1.5.0; 6.4.0.0 up to, but not including, 6.4.2.0 | 5.2.0.0, 5.2.7.0, 6.1.5.0, 6.4.2.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (arista.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (arista.com) |
| CVSS 3.1 | 9.6 | Critical | CNA (arista.com) |
Official description
An unauthenticated actor with network access to the private HA interconnect may trigger sensitive HA peer functions without verification. This could result in elevated command execution on Edge units where HA is enabled.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
References
Other vulnerabilities in VeloCloud Edge
- 8.0 High severity
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.1 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 10.0 Critical severity
- 9.8 Critical severity
- 8.2 High severity
Spotted an error? Tell us.