On this page (9 sections)
On November 2, 2026, the Debian Security Team published DSA-6604-1, a security update for Incus, the system container and virtual machine manager. Debian says multiple issues were found that could lead to a bypass of security or authorization restrictions, denial of service, privilege escalation or information disclosure.
If you run Incus on Debian 13 (trixie), for example to host containers or VMs for websites, staging servers or customer workloads, you should plan to update soon. The advisory is short and the details are thin, so this article separates what is confirmed from what is still unknown.
At a glance
What Debian has said
The advisory describes Incus as a system container and virtual machine manager and states that multiple security issues were discovered. It lists four possible impact classes: bypass of security or authorization restrictions, denial of service, privilege escalation and information disclosure. For the stable distribution, trixie, the problem is fixed in version 6.0.4-2+deb13u12, and Debian recommends upgrading the incus packages.
That is the full extent of the primary source. As of this writing the advisory gives no CVE identifiers, no severity ratings, no description of individual bugs and no statement about exploitation. Only one publisher (Debian itself) covers the story so far, so treat the impact list as Debian's summary and not as a confirmed description of any single flaw.
Why this class of bug matters for Incus hosts
Incus manages containers and virtual machines, so it sits at the boundary between workloads and the host. Authorization bypass and privilege escalation bugs in a manager like this can matter because the whole point of the tool is to keep workloads and users separated from each other and from the host. If someone can act beyond their intended permissions, a compromise of one container or one limited account could become a bigger problem.
Denial of service in a manager can mean containers or VMs cannot be started, stopped or managed. Information disclosure could expose data from other instances or from the host. Which of these apply to your setup depends on the specific bugs, which Debian has not detailed yet.
Who is exposed
- Debian 13 (trixie) systems with the incus package installed, where the installed version is older than 6.0.4-2+deb13u12.
- Hosting providers, agencies and developers who use Incus to run shared or multi-tenant containers and VMs, where several users or workloads rely on its isolation.
- Teams where people other than administrators can manage instances or reach the Incus API. The advisory does not say what access is required, so it is sensible to treat these hosts as a priority until details appear.
The advisory only names trixie. It does not mention other Debian releases or other distributions. If you install Incus from another source, such as a third-party repository or a different distribution's packages, check that source for its own advisory instead of assuming this fix applies.
How to check your version
This read-only command shows the installed Incus package version on Debian. A version older than 6.0.4-2+deb13u12 on trixie means the fix is not yet applied.
dpkg -l incus | grep '^ii'You can also ask apt which version is installed and which is available from your configured repositories. Compare the Candidate line with 6.0.4-2+deb13u12.
apt policy incusWhat to do now
- Identify every Debian host that runs Incus, including build servers, lab machines and hosting nodes.
- Run the version checks above and note any host older than 6.0.4-2+deb13u12 on trixie.
- Schedule the update for the first available maintenance window, prioritizing multi-tenant or internet-reachable hosts.
- Update the incus packages with apt (commands below).
- After the update, confirm the new version and that your containers and VMs are running as expected.
- Review who has access to manage Incus and remove access that is no longer needed.
- Watch the Debian security tracker page for incus, where CVE identifiers and details may appear.
This updates package lists and then upgrades only the incus packages. Run it as root or with sudo on a trixie host.
sudo apt update
sudo apt install --only-upgrade incusAfterwards, run the version check again to confirm you are on 6.0.4-2+deb13u12 or newer.
Detection and monitoring
Because the advisory gives no indicators and no exploit details, there is no specific log pattern to search for. General hygiene still helps: review authentication and API access logs on Incus hosts for unexpected clients, check for unexpected new instances, profiles or privileged settings, and watch for unexplained restarts or resource exhaustion that could point to denial of service.
Keep an eye on the Debian security tracker for incus, which the advisory points to for detailed status. When CVE identifiers are assigned, you will be able to map each one to its exact impact and conditions, and decide whether any extra mitigation is needed.
Incus hosts often sit next to public websites. If any of your hosted sites run on these systems, a free security scan and certificate and DNS monitoring can help you notice changes on the outside, though they cannot see inside a container host or confirm whether this issue was used against it.
What we do not know yet
- The CVE identifiers and CVSS scores for the individual issues.
- Which impact (authorization bypass, denial of service, privilege escalation or information disclosure) maps to which bug.
- Whether any of the issues can be triggered remotely or without authentication.
- Whether the issues are being exploited. The advisory does not say.
- Whether other Debian releases or other distributions are affected.
We will not guess at these. If you need to decide between updating now and waiting for details, update now: the fix is available, the change is a single package, and the advisory itself recommends it.
Keep your servers on a patching routine
Advisories like this one are easier to handle when patching is routine. For a broader view of keeping the servers behind your sites in good shape, see our small business website security guide and the latest posts on the Webforta security blog.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
