External risk intelligence

Incus Certificate and Token Exposure Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130783

Incus is a system container and virtual machine manager typically deployed on internal infrastructure or private cloud environments for virtualization management. While it uses network-accessible APIs, these services are generally restricted to administrative or internal management networks and are not intended to be exposed directly to the public internet.

Information Disclosure

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory describes a security flaw in Incus, a system container and virtual machine manager, that could allow unauthorized access and control. The vulnerability involves the improper handling of sensitive information and permissions, potentially enabling restricted clients to gain full server access or disrupt operations. The primary concern is to confirm if this technology is in use and assess potential exposure.

  • Sensitive data exposure and unauthorized control.
  • Potential for unauthorized server access and disruption.
  • Confirm relevance and assess exposure to Incus.

Attack Path

How an attacker could exploit the issue

An attacker with limited access could begin by subscribing to default project event streams within Incus. These streams expose sensitive information, including cluster join tokens and certificates, which can then be used to enroll unrestricted certificates. This allows the attacker to gain full control of the server or cancel critical token operations.

  • Requires limited client access.
  • Triggers by subscribing to event streams.
  • Results in full server access or token control.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could expose sensitive information like certificate and cluster join tokens through the event stream. Additionally, it may allow unauthorized cancellation of operations, potentially leading to full server access when accessed by restricted clients.

  • Certificate and cluster join tokens.
  • Subscription to event stream, skipping authorization.
  • Unrestricted server access.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Incus platform's default project event stream may expose sensitive tokens and allow unauthorized operation cancellations, potentially granting full server access. Owners of Incus deployments must identify instances, confirm reachability and business criticality, and assign an accountable owner to plan remediation.

  • Incus deployment owners.
  • Verify token exposure and unauthorized access.
  • Plan phased remediation based on risk.

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?

Incus is an open-source tool used for managing system containers and virtual machines. It functions as a lightweight virtualization manager that allows administrators to create, run, and orchestrate isolated operating system environments on a single host or across a cluster of servers.

What kind of vulnerability is CVE-2026-130783?

This vulnerability is classified as CWE-200, which refers to the exposure of sensitive information to an unauthorized actor. In this case, the software unintentionally shares security tokens and certificates through its event monitoring system and fails to enforce permission checks for certain administrative tasks.

How can an attacker trigger this security flaw?

An attacker needs existing restricted access to the system to exploit this. By subscribing to the default project event stream, they can intercept sensitive data like cluster join tokens. Notably, simply having access to the server is not enough; the vulnerability specifically relies on the software incorrectly broadcasting this data and failing to restrict who can cancel operations.

Is my Incus deployment at risk?

According to Halo Surface Signal, Incus is typically deployed on internal infrastructure or private cloud networks for management tasks. While the vulnerability is critical, it is unlikely to be exposed if your instances are not directly accessible from the public internet. You should evaluate your network configuration to confirm if these management APIs are reachable by untrusted users.

What should I do if I am running Incus?

First, identify all active Incus instances within your environment. Verify who currently has access to these systems, as the flaw requires a user with at least limited permissions to succeed. Once identified, assign an owner to oversee the update process and monitor official project guidance for remediation steps.

References