CVE
Incus root command execution via LXC config injection
Incus before 7.6.0 builds instance configuration from values in an image's config.json, and since 7.5.0 that parsing applies to any image carrying one, not only OCI images. Fixed in 7.6.0.
- 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. Values from an OCI image's config.json (environment, entrypoint, working directory) are used to build the instance configuration Since 7.5.0, config.json is parsed for any image carrying one, not only OCI images
Summary
Incus before 7.6.0 contains a configuration injection vulnerability that allows users who can launch instances from controlled images to inject LXC directives by embedding line breaks in OCI config.json values or oci.entrypoint and oci.cwd keys. Attackers can add liblxc hooks or crafted tmpfs lxc.mount.entry fields to run commands as root on the host or bind-mount host paths, even from restricted projects.
Who should check
Teams running Incus before 7.6.0 that let users launch instances from OCI or imported images, including in restricted projects
Not fixed by: Restricting restricted.images.servers does not stop importing a local image tarball.
“Affected versions < v7.6.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 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.
Values from an OCI image's config.json (environment, entrypoint, working directory) are used to build the instance configuration Since 7.5.0, config.json is parsed for any image carrying one, not only OCI imagesUpgrade 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-130786 (Incus before 7.6.0 LXC Configuration Injection via OCI Image Config), 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-130786 (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):
- Values from an OCI image's config.json (environment, entrypoint, working directory) are used to build the instance configuration (source: https://github.com/lxc/incus/security/advisories/GHSA-3wxw-5gh2-j2x2)
- Since 7.5.0, config.json is parsed for any image carrying one, not only OCI images (source: https://github.com/lxc/incus/security/advisories/GHSA-3wxw-5gh2-j2x2)
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-130786 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130786 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-3wxw-5gh2-j2x2
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-130786
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-130786"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
fixed in 7.6.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · lxc/incus · Advisory GHSA-3wxw-5gh2-j2x2 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130786 |
| Record | NVD · CVE-2026-130786 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130786
Is CVE-2026-130786 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?
Values taken from an image's config.json, such as environment, entrypoint and working directory, are used to build the Incus instance configuration. The stated impact is that an attacker can run arbitrary commands as root on the host or bind-mount arbitrary host paths into the container.Source: github.com
Which versions are affected by CVE-2026-130786?
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. Since 7.5.0, config.json is also parsed for non-OCI images that carry such a file, not only OCI images. To check the installed version, run incus --version and compare it with 7.6.0.Source: github.com
How do I fix CVE-2026-130786?
Upgrade Incus to 7.6.0 or later, which is the fixed version listed for this vulnerability.Source: github.com