Quick answers
- Is CVE-2026-86108 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86108 being exploited in the wild.
- How severe is CVE-2026-86108?
- High severity, with a CVSS score of 8, published 16 September 2026.
- Which products and versions are affected?
- Arista Velocloud Edge 6.4.1.x and below in 6.4.x train; 6.1.4.x and below in 6.1.x train; 5.2.6.x and below in 5.2.x train; all prior releases.
- Is there a fix for CVE-2026-86108?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-86108 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-86108?
- Check whether you run Arista Velocloud Edge at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an OS command injection vulnerability (CWE-78) in VeloCloud Edge's management and configuration workflows. Insufficient input validation on parameters passed through management requests or configuration values allows them to be interpreted as operating-system commands. The vulnerability requires the attacker to either control a compromised VeloCloud Orchestrator (management server) or possess valid administrative credentials to submit malicious parameters through the management interface. Exploitation results in command execution with elevated privileges on the edge device. The flaw was discovered internally by Arista and is not known to be exploited in the wild. Patched versions are available: 7.0.0+, 6.4.2+, 6.1.5.0+, and 5.2.7.0+.
Affected products
- Arista VeloCloud Edge 6.4.1.x and below in 6.4.x train; 6.1.4.x and below in 6.1.x train; 5.2.6.x and below in 5.2.x train; all prior releases
Timeline
- 2026-09-09: disclosed: Initial advisory release
- 2026-09-16: disclosed: CVE published
- 2026-09-22: other: CSAF JSON file added to advisory