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).
do firstApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Is CVE-2026-93952 being exploited?
Yes. CVE-2026-93952 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
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.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 22 Sept 2026 (SSVC 2.0.3).
timeline
- 22 Sept 2026Added to CISA KEV (exploited in the wild)
- 22 Sept 2026CISA SSVC assessment: exploitation active · same day later
- 22 Sept 2026Published · same day later
- 22 Sept 2026Analysed by vulneraibility.com · same day later
- 23 Sept 2026CVE record last updated · 1 day later
- 25 Sept 2026CISA remediation due date (US federal agencies) · 2 days later
- Advisoryarista.com /en/support/advisories-notices/security-advisory/24765-security-advisory-0183
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-93952
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.