External risk intelligence

Incus Authentication Bypass Allows Cluster-Level Access

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-130778

Incus is a system container and virtual machine manager typically used for infrastructure management and virtualization within internal data centers or private networks. While it uses network-based TLS communication, it is not designed to be exposed directly to the public internet in standard deployments, making internet-reachable exposure possible but less common than edge services or public-facing web applications.

Authentication Bypass

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Incus, a system for managing containers and virtual machines. The flaw allows unauthorized remote access to cluster-level controls by bypassing authentication mechanisms. This could potentially lead to significant compromise of the underlying infrastructure and its data.

  • Bypass security to gain unauthorized access.
  • Critical for infrastructure and data protection.
  • Confirm relevance and understand potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could bypass authentication by intercepting and manipulating TLS client connections to Incus. By appending a trusted certificate, such as the server's own certificate or that of another cluster member, to their presented TLS client chain, an attacker can impersonate a legitimate user or service. This allows them to gain unauthorized cluster-level access, circumventing standard authorization checks and potentially altering critical trust store configurations or influencing scriptlet-based authorization logic.

  • Unauthenticated network access required.
  • Appending certificate to TLS client chain.
  • Unauthorized cluster access and control.

Live Threat

Current exploitation, exposure, and threat context

An authentication bypass vulnerability in Incus could allow remote attackers to impersonate trusted certificates, granting them cluster-level access and the ability to modify trust store entries and influence authorization decisions. This could occur when the system is configured to accept untrusted certificates, potentially exposing sensitive cluster operations.

  • Cluster access and control.
  • Remote attackers bypass authentication.
  • Unauthorized access and modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

The remote authentication bypass vulnerability in Incus impacts cluster administration. Infrastructure or platform teams are likely responsible for managing Incus, with security teams needing to oversee its exposure and access controls. The first step is to identify all Incus deployments, determine their reachability and business criticality, and then ascertain the specific ownership for each instance to plan remediation.

  • Identify Incus deployment owners.
  • Verify network reachability and criticality.
  • Plan remediation based on exposure.

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 Incus and what is it used for?

Incus is an open-source software platform used for system container and virtual machine management. It provides a unified interface for infrastructure teams to create, run, and orchestrate isolated Linux environments. Organizations typically deploy it within data centers or private networks to handle high-density virtualization and simplify the lifecycle of compute resources.

How does CVE-2026-130778 work as an authentication bypass?

This vulnerability falls under Improper Authentication (CWE-287). It occurs because the system fails to correctly validate the full TLS certificate chain presented during a connection. An attacker can manipulate their client connection to include a trusted certificate, tricking the software into accepting the attacker's request as legitimate, which allows them to bypass identity checks and gain unauthorized administrative control.

What triggers the vulnerability in Incus?

The flaw is triggered when an attacker initiates a network connection to an Incus instance and appends a trusted certificate, such as a cluster member's or the server's own certificate, to their TLS client chain. This does not occur through standard, authorized API usage; it requires the specific, malicious act of injecting these credentials into the handshake process to deceive the server's trust logic.

Is my Incus deployment at risk according to Halo Surface Signal?

Halo Surface Signal notes that Incus is generally designed for internal management, not direct internet exposure. While it is not typically intended to face the public internet, any instance that is inadvertently reachable from outside your private network has a higher potential for impact. You should verify your network segmentation to ensure these management interfaces remain restricted to trusted internal access.

What should I do if I manage Incus?

Start by identifying all instances of Incus within your environment and mapping who owns each deployment. Verify the network reachability of these systems to confirm they are appropriately isolated from external access. Once you have a complete inventory and understand which servers are critical, collaborate with your platform teams to confirm the current version and prepare for security updates provided by the project maintainers.

References