On this page (7 sections)
A critical configuration injection flaw, CVE-2026-130786, affects Incus versions before 7.6.0. According to the NVD record, a user who can launch instances from images they control can inject LXC directives and end up running commands as root on the host, even from a restricted project.
If you run Incus on shared infrastructure, a hosting platform, or any setup where more than fully trusted people can launch instances, this deserves prompt attention. The record was published on 2026-11-18 and only one independent publisher covers the story so far, so details beyond the NVD description are limited.
What happened
The NVD entry describes a configuration injection problem in Incus. The project's own advisory is referenced as GHSA-3wxw-5gh2-j2x2. The research available to us contains only the NVD description, so we do not have the advisory text, a patch description, or any report of attacks in the wild.
Technical details in plain terms
Incus can run OCI-style images, and those images carry configuration such as a config.json file and the oci.entrypoint and oci.cwd keys. Incus turns that data into LXC configuration for the container. The weakness is that line breaks inside those values are not neutralized. LXC configuration is line based, so a value containing a newline can start a new, attacker-chosen directive instead of staying a harmless string. This is the general pattern behind CWE-74 injection bugs.
Per the NVD description, the injected directives can do two things:
- Add liblxc hooks, which run commands as root on the host.
- Add crafted tmpfs lxc.mount.entry fields, which can bind-mount host paths.
The description also states this works even from restricted projects. Restricted projects are normally the boundary operators rely on to let less trusted users create instances, so this flaw undermines that boundary.
Who is affected
Any Incus deployment running a version before 7.6.0 is within the affected range. The realistic risk depends on who can launch instances:
- Multi-tenant or shared hosts where users get restricted projects are the most exposed, since the flaw reportedly works across that restriction.
- Environments where users can import or supply their own images, including OCI images, face higher risk than those using only images you built and reviewed.
- A single-admin host that only launches images you fully trust has lower exposure, but it should still be updated.
How to check your exposure
Start with the installed version. This read-only command, run on each Incus host, prints the client and server versions. Anything below 7.6.0 is in the affected range.
incus versionThen review who can create instances. This read-only command lists projects so you can see which ones exist and which are used by less trusted users.
incus project listIf your Incus came from a distribution or third-party package, check which version that source ships, because the package version may not match the upstream release number you expect.
What to do now
- Run incus version on every host and note any version below 7.6.0.
- Upgrade Incus to 7.6.0 or later using your normal package source or release process.
- Until you can upgrade, restrict who can launch instances, and avoid launching images or OCI configurations from sources you do not fully trust.
- Review recently launched instances and the images they came from, especially in projects used by less trusted users.
- Look at instance configuration for unexpected raw LXC settings, hooks or mount entries that you did not add.
- If you find suspicious instances, treat the host as potentially compromised: preserve logs, rotate credentials and secrets reachable from the host, and rebuild if needed.
To inspect an instance's configuration for anything unexpected, this read-only command prints its settings. Replace NAME with the instance name and look for raw LXC entries, hooks or mount lines you did not set.
incus config show NAME --expandedDetection and monitoring afterwards
Because the impact is code execution as root on the host, watch for the signs of a host compromise rather than just container misbehavior: unexpected processes started by the Incus daemon, new files or users on the host, and host paths showing up inside instances. Keep an audit trail of who launched which instance and from which image, and review it regularly. Limit image sources, and prefer images you build or pin yourself.
For exposed management or application endpoints that sit on top of your container hosts, outside monitoring such as Webforta Monitor can alert you to uptime, certificate and DNS changes, though it cannot see inside a host or confirm this specific flaw. Our guide to what to do if a website is hacked covers response steps if you suspect a breach.
What is still unknown
- No exploitation in the wild is reported in the research, and the CVE is not marked in CISA KEV.
- We have not seen the vendor advisory text, so the exact fix details and any workarounds are unconfirmed.
- Only one independent publisher covers this so far, so treat details beyond the NVD description as unverified.
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.
