home / blog
2026-10-29 · critical
CVE-2026-114625: Critical Escalation in VeloCloud Orchestrator
Authenticated users escalate to operator on VeloCloud on-prem. CVSS 9.9 critical. Immediate action.

CVE-2026-114625 affects VeloCloud Orchestrator in on-premises deployments. The vulnerability allows any authenticated user to escalate privileges by acquiring operator role and accessing internal-only functionality. This escalation bypasses restrictions and enables access to components not intended for remote access, risking the integrity and availability of the orchestrator.
CVSS score is 9.9, critical level. The vulnerability was published by NVD on October 22, 2026. A relevant signal emerges from GitHub, where an offline detector was published on October 28 to identify exposure on on-premises instances. Hosted versions of VeloCloud have already been patched; on-prem deployments remain vulnerable until patching is applied.
On-prem administrators must contact the vendor to obtain updates and plan patching urgently. Use the GitHub detector to identify which instances are exposed. Meanwhile, review access logs and audit permissions of authenticated users, restricting privileges to accounts that genuinely require elevated access.
VeloCloud Orchestrator is the central management system for enterprise SD-WAN networks. An orchestrator compromise exposes the entire network infrastructure to the attacker, allowing configuration changes, traffic interception, and edge device control. This vulnerability's criticality reflects the product's crucial role in enterprise architectures.
At a glance
- What
- Privilege escalation in VeloCloud Orchestrator on-prem. Authenticated users can acquire operator privileges and access internal functionality not intended for remote access.
- Severity
- CVSS 9.9 (critical). Compromises confidentiality, integrity, and availability of the orchestrator and managed data.
- Affected versions
- VeloCloud Orchestrator on-prem. Hosted versions already patched as of publication date.
- Fix
- Patch available for hosted versions. For on-prem: contact vendor for security updates.
- Status
- Published NVD October 22, 2026. Offline detector on GitHub available since October 28 to identify exposure.
- Action
- On-prem: verify and apply patching urgently. Use detector to identify exposed instances. Review authenticated user permissions.
Sources: NVD, CVE-2026-114625