Quick answers
- Is CVE-2026-93952 exploited in the wild?
- Yes. CVE-2026-93952 is known to be exploited in the wild, first recorded on 22 September 2026. Treat it as urgent.
- How severe is CVE-2026-93952?
- Critical severity, with a CVSS score of 10, published 22 September 2026.
- Which products and versions are affected?
- Arista VeloCloud Orchestrator on-premises deployments.
- Is there a fix for CVE-2026-93952?
- 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-93952 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-93952?
- Check whether anything you run is named in the advisory. 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
The vulnerability is an improper input validation flaw in Arista VeloCloud Orchestrator (on-premises deployment). The vulnerability allows a remote attacker without authentication to submit maliciously crafted input that bypasses input validation controls and grants access to privileged internal functionality. The attack requires network access to the VCO host but no prior authentication or user interaction. Successful exploitation enables an attacker to compromise the confidentiality, integrity, and availability of the orchestrator and all data it manages. The vulnerability is known to be actively exploited in the wild.
Affected products
- Arista VeloCloud Orchestrator on-premises deployments
Timeline
- 2026-09-22: disclosed
- exploited