External risk intelligence

SolusVM 2 Server-Side Template Injection Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-105474

SolusVM 2 is a virtualization management platform designed for administrative control and server management. Such platforms are typically deployed as internet-facing web interfaces to allow administrators to manage infrastructure remotely. Because the application functions as a centralized gateway for managing multiple servers, it is commonly exposed to the internet, making this interface a likely target for remote access.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A server-side template injection vulnerability in SolusVM 2 could allow authenticated users to run unauthorized commands on the system with root privileges. This type of issue in a server management platform warrants attention to confirm if your organization utilizes this technology and is exposed.

  • Allows code execution for authenticated users.
  • It affects server management, a critical function.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker who can authenticate to SolusVM 2 could exploit a server-side template injection vulnerability to achieve arbitrary code execution. This would allow them to run commands on the server with root privileges.

  • Attacker must be authenticated.
  • Attacker triggers vulnerability via template injection.
  • Risk of arbitrary code execution as root.

Live Threat

Current exploitation, exposure, and threat context

A server-side template injection vulnerability could allow remote authenticated users to execute arbitrary code as root on the SolusVM 2 system. This means that an attacker who has already gained some level of access to the system might be able to run commands with the highest privileges.

  • System root access.
  • Authenticated user may inject code.
  • Full system compromise possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world impact for this vulnerability will likely fall to platform or infrastructure teams managing the SolusVM 2 deployment. The first practical step is to identify all SolusVM 2 instances, confirm their external reachability and business criticality, and then locate the accountable owner for each instance to begin remediation planning based on associated risk.

  • Platform or infrastructure teams should own the issue.
  • Verify SolusVM 2 instance reachability and criticality.
  • Plan remediation based on risk and ownership.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is SolusVM 2?

SolusVM 2 is a virtualization management platform. Organizations use it to centralize administrative control over virtual servers, acting as a gateway for managing infrastructure across multiple environments.

What does CVE-2026-105474 mean for the software?

This vulnerability is classified as CWE-1336, or improper neutralization of special elements used in a template engine (Server-Side Template Injection). In SolusVM 2, this flaw allows a user to inject malicious instructions that the server unintentionally processes, potentially granting them unauthorized command execution at the root level.

How is this vulnerability triggered?

An attacker must already have authenticated access to the application to initiate the injection. Simply reaching the login page or sending unauthenticated web requests does not trigger the flaw; the process requires a user session to interact with the vulnerable template components.

Why is SolusVM 2 considered a likely target?

According to Halo Surface Signal, SolusVM 2 is designed for remote infrastructure management and is frequently deployed as an internet-facing interface. Because it serves as a central control point for critical systems, its exposure to the internet increases the likelihood that it could be targeted by remote attackers.

Do I need to take action if I use SolusVM 2?

Yes. Platform and infrastructure teams should prioritize identifying all instances of SolusVM 2 within their environment. Once identified, confirm the external accessibility and business criticality of each instance, then coordinate with the appropriate system owners to initiate remediation planning.

References