Compromise of VeloCloud Orchestrator gives attackers privileged control of SD‑WAN orchestration and network infrastructure, impacting many enterprise networks.
CVE-2026-93952
Remote privilege escalation in VeloCloud Orchestrator (on‑prem).
Is CVE-2026-93952 being exploited?
Not confirmed. CVE-2026-93952 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-93952?
CVE-2026-93952 is rated Critical with a CVSS score of 9.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-93952?
Yes. A fix has been recorded for CVE-2026-93952. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-93952 affect?
CVE-2026-93952 affects VeloCloud Orchestrator (VCO) on‑prem, VMware SD‑WAN VCO (hosted versions patched). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-93952?
Apply vendor patch immediately; isolate VCO, rotate creds, audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can access privileged internal functionality, compromise the VCO host and orchestrated data (confidentiality, integrity, availability).
Immediate action required
- affected>= 5.2.0 and <= 5.2.3.15
- affected>= 6.1.0 and <= 6.1.3.7
- affected>= 6.4.0 and <= 6.4.2.7
- affected>= 7.0.0 and <= 7.0.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.