Skip to main content
Menu
CVEs

CVE

Incus auth bypass in guest API allows container impersonation

Affects Incus 7.3.0 before 7.6.0 when containers share UID ranges (security.idmap.isolated not set) and an ancestor process has an empty command line. Fixed in 7.6.0.

CVE-2026-130785EUVD-2026-129133Published Updated Summary written by a model

8.4HighCNA
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. Incus versions 7.3.0 up to before 7.6.0 An ancestor process has an empty command line, so the daemon falls back to the cgroup path Containers share UID ranges because security.idmap.isolated is not set

Summary

Incus from 7.3.0 before 7.6.0 contains an authentication bypass vulnerability in the /dev/incus guest API that allows a process in one container to impersonate another by creating a cgroup named with a forged lxc.monitor. component. Attackers can read the target container's user.* and cloud-init.* configuration and devices, subscribe to its events, mark it ready, and export images across projects.

Who should check

Operators running Incus 7.3.0 before 7.6.0 with multiple containers on one host, including Go builds of github.com/lxc/incus/v7/cmd/incusd

“Since 7.3.0, when an ancestor's command”

github.com

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity8.4/10CVSS 8.4
  • No patch0/5No signal

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 33 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Incus versions 7.3.0 up to before 7.6.0 An ancestor process has an empty command line, so the daemon falls back to the cgroup path Containers share UID ranges because security.idmap.isolated is not set
  • 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-130785 (Incus 7.3.0 before 7.6.0 Guest API Container Impersonation via Forged Cgroup), 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-130785 (entry last updated 2026-11-18):
Affected:
- Go package github.com/lxc/incus/v7/cmd/incusd: from 7.3.0, fixed in 7.6.0
Fixed versions: 7.6.0.
Conditions (all must be true for the bug to be hit):
- Incus versions 7.3.0 up to before 7.6.0 (source: https://github.com/lxc/incus/security/advisories/GHSA-v736-5xp3-jghf)
- An ancestor process has an empty command line, so the daemon falls back to the cgroup path (source: https://github.com/lxc/incus/security/advisories/GHSA-v736-5xp3-jghf)
- Containers share UID ranges because security.idmap.isolated is not set (source: https://github.com/lxc/incus/security/advisories/GHSA-v736-5xp3-jghf)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130785 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130785 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-v736-5xp3-jghf
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-130785
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-130785"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lxc/incus · Advisory GHSA-v736-5xp3-jghf
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130785
RecordNVD · CVE-2026-130785

Corrections

None so far.

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

Questions about CVE-2026-130785

Is CVE-2026-130785 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 process in one container can impersonate another container through the guest API. It can read that container's user.* and cloud-init.* configuration and device list, subscribe to its events, mark it ready, and export its images when security.guestapi.images is enabled.Source: github.com

Which versions are affected by CVE-2026-130785?

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

Am I affected, and how do I check?

Incus versions from 7.3.0 up to, but not including, 7.6.0. Run incus version to see the installed version. The setup also matters: containers must share the same UID range, which is the default unless security.idmap.isolated is set.Source: github.com

How do I fix CVE-2026-130785?

Upgrade Incus to 7.6.0 or later, the fixed version listed for this vulnerability. The sources checked do not name a workaround.Source: github.com

More CVEs