Skip to main content
Menu
CVEs

CVE

Incus privilege escalation via rebuilt never-started containers

Affects Incus before 7.6.0, specifically unprivileged containers that are rebuilt before they have ever been started. Fixed in Incus 7.6.0.

CVE-2026-130774Published Updated Summary written by a model

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 7.6.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. The instance is an unprivileged container that is rebuilt before it has ever been started.

Summary

Incus before 7.6.0 contains a privilege escalation vulnerability: rebuilding a never-started unprivileged container makes it boot without a user namespace. Root processes inside the container run as host uid 0, keeping capabilities like sys_module, with no device cgroup restriction, letting them load kernel modules and compromise the host.

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach10/20Affects Go packages
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    The instance is an unprivileged container that is rebuilt before it has ever been started.
  • Upgrade to a fixed version: 7.6.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130774 (Incus before 7.6.0 Privilege Escalation via Rebuild of Never-Started Container), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130774 (entry last updated 2026-11-18):
Affected:
- Go package github.com/lxc/incus/v7/cmd/incusd: fixed in 7.6.0
Fixed versions: 7.6.0.
Conditions (all must be true for the bug to be hit):
- The instance is an unprivileged container that is rebuilt before it has ever been started. (source: https://github.com/lxc/incus/security/advisories/GHSA-9c46-v3hw-v6m8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-130774 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130774 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/lxc/incus/security/advisories/GHSA-9c46-v3hw-v6m8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130774
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130774"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lxc/incus · Advisory GHSA-9c46-v3hw-v6m8
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130774
RecordNVD · CVE-2026-130774

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130774

Is CVE-2026-130774 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A container that is rebuilt before it has ever been started boots with no user namespace. A root process inside that container then gets host root, with dangerous capabilities such as sys_module and raw I/O, so it can load a kernel module or write host devices and fully compromise the host.Source: github.com

Which versions are affected by CVE-2026-130774?

github.com/lxc/incus/v7/cmd/incusd (Go): before 7.6.0.Source: cve.now feed data

Am I affected, and how do I check?

Incus versions before 7.6.0 are affected, but only for unprivileged containers that are rebuilt before they have ever been started. To check, run the Incus version command on the host to see the installed release, and check whether the instance is an unprivileged container.Source: github.com

How do I fix CVE-2026-130774?

Upgrade Incus to 7.6.0 or later, which is the fixed version for this vulnerability.Source: github.com

More CVEs