CVE-2026-16812: VeloCloud Orchestrator OS Command Injection
VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator.
This functionality was intended to be for internal use only and is not intended to be remotely accessible.
Hosted and Dedicated versions of VCO have already been patched in advance of this notice going out.
This issue was discovered externally and is known to be actively exploited.
Security readout for executives and security teams
Plain-English summary
A remotely reachable, unauthenticated flaw in affected on-premises VeloCloud Orchestrators can expose privileged internal functions and compromise the orchestrator host and managed data. Because exploitation is confirmed and potential impact spans confidentiality, integrity, and availability, exposed deployments require immediate attention.
Executive priority
Emergency priority. Assign accountable owners immediately, reduce network exposure, follow vendor remediation, and investigate affected systems for compromise. Confirm completion through version and access validation rather than relying solely on patch deployment reports.
Technical view
CVE-2026-16812 is a CWE-78 OS command injection issue affecting specified VeloCloud Orchestrator On-Prem releases. Its CVSS 3.1 score is 10.0: network-accessible, low complexity, no privileges or user interaction required, with scope change and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to VeloCloud Orchestrator On-Prem versions 5.2.0, 6.1.0, 6.4.0, and 7.0.0 identified by the vendor. Risk is greatest where orchestrator functionality is remotely reachable. Hosted and Dedicated VCO versions were patched before disclosure.
Exploitation context
Active exploitation is explicitly reported by the vendor, and CVE-2026-16812 is identified in CISA's Known Exploited Vulnerabilities catalog. The supplied evidence does not describe attacker identities, exploitation scale, indicators of compromise, or observed victim sectors.
Researcher notes
The evidence establishes remote, unauthenticated command injection, affected on-premises releases, maximum CVSS severity, and active exploitation. It does not provide vulnerable endpoints, technical root cause, exploit mechanics, indicators, corrected version numbers, or attribution. Researchers should use the vendor advisory for authorized defensive validation details.
Mitigation direction
Identify affected on-premises VCO deployments and immediately restrict remote access to trusted administrative networks.
Consult Security Advisory 0144 for vendor-approved corrected versions and remediation instructions.
Apply the vendor remediation urgently, prioritizing Internet-reachable or broadly accessible orchestrators.
Treat suspected exploitation as a potential host and managed-data compromise; activate incident-response procedures.
Confirm Hosted or Dedicated environments are vendor-patched rather than assuming coverage.
Validation and detection
Inventory every VCO deployment, hosting model, installed version, and externally reachable interface.
Compare each on-premises version and configuration with Security Advisory 0144.
Verify orchestrator access is limited to authorized administrative networks and identities.
Review available host, authentication, network, and orchestrator telemetry for unexplained privileged activity.
After remediation, verify the installed version and repeat exposure checks.
Escalate anomalies for forensic investigation because published indicators are absent from the supplied evidence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.