Skip to content
Blog

Incus · LXC · OCI

Incus CVE-2026-130778 (10.0) and CVE-2026-130786 (9.9): Certificate Impersonation and LXC Directive Injection, Fixed in 7.6.0

Incus before 7.6.0: CVE-2026-130778 (10.0) lets anyone authenticate as a trusted certificate, CVE-2026-130786 (9.9) gives root command execution on the host.

4 min readCVE-2026-130778CVE-2026-130786

On November 18, 2026, NVD published two critical CVEs in Incus, the container and VM manager forked from LXD. Both are fixed by the same release: Incus 7.6.0.

They break two different boundaries:

  • CVE-2026-130778 breaks API authentication: a remote attacker can pose as any trusted certificate, including the server's own.
  • CVE-2026-130786 breaks isolation: a user who can launch an instance from an image they control gets root command execution on the host, even from a restricted project.

It's Incus's second critical batch in a month, after three 9.9 isolation escapes in October.

CVECVSS 3.1CVSS 4.0TypePrivileges
CVE-2026-13077810.0 — AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H10.0Improper authentication (CWE-287)None
CVE-2026-1307869.9 — AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H9.4Injection (CWE-74)Low

Scores published by VulnCheck (CNA). NVD has marked both entries Deferred, meaning they won't be analyzed. Neither is in CISA KEV at the time of writing.


CVE-2026-130778 — authenticating with someone else's certificate

Incus authenticates API clients by TLS client certificate: each trusted certificate is recorded in the server's trust store.

According to NVD, an attacker can authenticate as any trusted certificate by appending that certificate's public part to the TLS client chain they present. A public certificate isn't a secret; seeing it once is enough.

The worst case NVD describes: appending the certificate of the server itself or of a cluster member, which grants cluster-level access. From there the attacker can:

  • bypass authorization rules;
  • modify trust store entries (and so add themselves for good);
  • influence authorization decisions made by scriptlets.

The scope change (S:C) makes sense: cluster access to Incus means control of every instance it hosts.


CVE-2026-130786 — line breaks that turn into LXC directives

Incus can launch instances from OCI images (the Docker image format). Values from the OCI config.json, plus the oci.entrypoint and oci.cwd keys, end up in the container's LXC configuration.

Per NVD, those values aren't filtered: a line break in a value lets you append your own LXC directives. NVD lists two outcomes:

  • adding liblxc hooks, which run as root on the host;
  • adding a crafted tmpfs lxc.mount.entry to bind-mount host paths into the container.

And it works even from restricted projects, which is precisely the setting meant to keep an Incus user away from the host.

Condition: being able to launch an instance from an image you control. On a multi-tenant platform, a CI runner or a shared lab, that's a routine permission.


Affected versions

CVEAffected versions (NVD)First version outside the range
CVE-2026-130778before 7.6.07.6.0
CVE-2026-130786before 7.6.07.6.0

NVD hasn't published a CPE configuration. Details are in the project's GitHub advisories: GHSA-xg75-xf37-cph9 (130778) and GHSA-3wxw-5gh2-j2x2 (130786). If you run Incus from distribution packages (Debian, Ubuntu, Zabbly…), confirm the packaged version actually carries these fixes.

incus version

Detection

  • Trust store: incus config trust list, compared against the clients you actually enrolled. Any unknown entry is a strong signal.
  • API logs: authenticated sessions using the identity of the server or a cluster member, from an address that isn't theirs.
  • OCI instances: oci.entrypoint and oci.cwd keys containing line breaks; inspect them with incus config show <instance>.
  • Host: root processes spawned by unexpected LXC hooks, unusual tmpfs or bind mounts inside containers.

Mitigation

  1. Upgrade to Incus 7.6.0 or later, on every cluster member.
  2. Don't expose the Incus API beyond admin workstations: CVE-2026-130778 needs no account.
  3. Restrict image sources: until you've patched, only allow trusted registries and images for restricted projects.
  4. Audit the trust store after upgrading: the flaw allowed modifying it, and the fix doesn't remove what was added.

Why Continuous Monitoring of Your Container Infrastructure Matters

Two critical Incus batches in a month, all on isolation or authentication boundaries. A container host often isn't in any security inventory: it belongs to the infrastructure team, not to whoever watches the alerts.

With cveo.tech, add your Incus hosts and their versions to your inventory, and get an alert as soon as a CVE affects them.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.