What happened
Incus is an open source manager for Linux containers and virtual machines, developed by the Linux Containers community. On October 29, 2026, the Incus project published four security advisories on GitHub, all rated “critical”. The fix is in version 7.6.0. The US National Vulnerability Database (NVD) published the four matching CVE entries on November 18, 2026.
- CVE-2026-130778 (CVSS 10.0): authentication bypass. Anyone who can reach the Incus network interface (HTTPS API) can pose as any trusted client, or even as the server itself or a cluster member.
- CVE-2026-130784 (CVSS 9.9): a user restricted to one project can create and modify resources in the default project. According to the vendor, this can lead to code running as root on the host.
- CVE-2026-130780 (CVSS 9.9): when an instance is moved from a malicious server, the receiving server can be made to write outside its intended directories. With dir storage pools, the vendor says this means full host compromise.
- CVE-2026-130771 (CVSS 9.9): a crafted backup or image can contain special files or links that let a restricted user read or overwrite files on the host.
At the time of writing, neither the vendor, the CISA KEV catalog nor the EU vulnerability database EUVD report any of these flaws being exploited. The details have been public since late October, though, so do not put off the update.
Why it is dangerous
The most serious flaw is CVE-2026-130778. Incus identifies clients by their certificates. The server did check that the client holds the key for the first certificate it presents, but then compared the entire chain the client sent against its trusted certificates. Think of a doorman who checks your ID card, then spots a photocopy of the CEO’s badge in your stack of papers and lets you in with the CEO’s access.
The attacker needs no login at all, only network access to the API. According to the vendor, the server’s own certificate is handed to anyone who connects. The result can be cluster-level access, a complete authorization bypass, and renewing or deleting trusted certificates. The forged certificates also reach the authorization scriptlets, so even a client logged in with a token or through OIDC can influence their decisions.
The other three flaws require low privileges, such as a restricted certificate for one project, or moving an instance from a malicious server. They can still lead to code running as root on the host, overwritten host files, corrupted storage, leaks of other projects’ data or a crashed service. Whoever controls the host controls every container and virtual machine on it.
The CVSS score rates severity on a scale of 0 to 10. The scores of 10.0 and 9.9 (CVSS 3.1) were assigned by VulnCheck, and the vendor lists the same values in its advisories. The flaws are not in the CISA KEV catalog, where the US agency CISA lists vulnerabilities with confirmed exploitation. An EPSS value, which estimates the likelihood of exploitation in the next 30 days, is not yet available.
Who is affected
This affects anyone running Incus older than 7.6.0. The vendor lists the affected package as github.com/lxc/incus/v7/cmd/incusd, which is the server component (the incusd daemon). According to the vendor, the certificate flaw has been present since the first Incus release.
Incus runs on company virtualization servers, at smaller hosting providers and in private clouds, in multi-server clusters and in test labs. The risk depends on your setup:
- Highest: the network API (HTTPS) is reachable from the internet or an untrusted network. CVE-2026-130778 alone is enough here, with no login required.
- Setups with multiple customers or teams using restricted certificates or restricted projects (CVE-2026-130784 and CVE-2026-130771).
- Anyone who moves or copies instances from third-party or unverified servers (CVE-2026-130780).
If you only use Incus locally on a single machine, with no network API and no other users, the risk is much lower. Update anyway: the vendor says the certificate flaw also affects the connection between the host and its virtual machines.
How to check if you are affected
Check the server version with this command. It only reads, it changes nothing:
incus version
The Server version line must show 7.6.0 or higher. To check the installed package, depending on your distribution:
dpkg -l | grep incus
rpm -q incus
To see whether the network API is enabled and where it listens:
incus config get core.https_address
sudo ss -tlnp | grep incusd
An empty result from the first command means the network API is off. If it returns something like :8443, it listens on all interfaces and you should verify your firewall does not expose it to the internet. In a cluster, check every server separately (incus cluster list shows them).
How to fix it
The vendor fixed all four flaws in version 7.6.0. The flaws are not in the CISA KEV catalog, so CISA has not set a mandatory remediation deadline. Recommended order of steps:
- Right away, restrict access to the Incus HTTPS API to trusted addresses only, for example with a firewall or behind a VPN. For CVE-2026-130778 the vendor says this is the only workaround. No configuration setting avoids it.
- Back up your configuration and important instances and schedule a short maintenance window.
- Update Incus to 7.6.0 or later from the repository you installed it from (for example
apt updateandapt install incus). In a cluster, update every member. If your distribution package does not have 7.6.0 yet, ask the distribution maintainers whether they have backported the fix. - After updating, confirm the version with
incus version.
Until the update is in place, the vendor lists these temporary measures:
- In restricted projects, set
restricted.networks.accessto the list of existing networks they may use. This blocks the creation of new networks (CVE-2026-130784). For other resource types, the only option is enabling the matchingfeatures.*key on the project, which usually requires the project to be empty. - Do not allow untrusted tenants with restricted access to create images, instances or backups (CVE-2026-130771).
- Only move instances from trusted servers (CVE-2026-130780).
What if you may already be compromised
The vendor has not published specific indicators of compromise yet. If your API was reachable from an untrusted network or you have tenants with restricted access, review the following:
- Trusted certificates (
incus config trust list): unknown entries, unexpectedly renewed or missing certificates. - Networks, profiles and images in the default project (
incus network list --project default,incus profile list --project default,incus image list --project default). Look especially for networks none of your staff created and for networks with theraw.dnsmasqkey set (shown byincus network show NAME). - Imported instances: the vendor says operators can check their volume outside the
rootfsdirectory for special files, hard links or symlinks in place of regular files. - Service logs (
journalctl -u incus): unexpected crashes, stuck imports, transfers from unknown servers. - Unknown files and volumes on dir storage pools.
If you find anything suspicious, disconnect the server from the network, preserve the evidence and bring in an incident response specialist. If code may have run as root, the host can no longer be trusted. The safest path is to reinstall it, restore from verified backups and replace both server and client certificates.
Sources
- Authentication and authorization bypass through unverified client certificate chains · Adv ↗
- Restricted clients can create and access resources in the default project · Advisory · lxc ↗
- Path traversal, crash and storage pool restriction bypass through dependent volumes in mig ↗
- Restricted project users can read or overwrite host files through special files, hard link ↗
- NVD: CVE-2026-130778 ↗
- NVD: CVE-2026-130784 ↗
- NVD: CVE-2026-130780 ↗
- NVD: CVE-2026-130771 ↗
- ENISA EUVD EUVD-2026-129123 ↗
- ENISA EUVD EUVD-2026-129131 ↗
- ENISA EUVD EUVD-2026-129127 ↗
- ENISA EUVD EUVD-2026-129117 ↗