Skip to main content
Menu
CVEs

CVE

Incus authorization bypass in guest API image export

Affects Incus before 7.6.0 in containers with security.guestapi.images=true, which lets a container root read images from other projects. Fixed in 7.6.0.

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

8.2HighCNA
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. Container has the guest-API image entitlement enabled (security.guestapi.images=true)

Summary

Incus before 7.6.0 contains an authorization bypass vulnerability in the /dev/incus guest-API image export handler that fails to pin the project parameter to the guest's own project. Container root users with the guest-API image entitlement can supply another project in the project query parameter to export public or cached images, including non-public images pulled from authenticated remotes.

Who should check

Teams running Incus before 7.6.0 that give containers the guest-API image entitlement (security.guestapi.images), including anyone shipping the github.com/lxc/incus Go package

“Incus guest-API image export ignores the guest's project, exposing other projects' images”

github.com

cve.now Index

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

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 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.

    Container has the guest-API image entitlement enabled (security.guestapi.images=true)
  • 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-130775 (Incus before 7.6.0 Cross-Project Image Disclosure via /dev/incus Image Export), 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-130775 (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):
- Container has the guest-API image entitlement enabled (security.guestapi.images=true) (source: https://github.com/lxc/incus/security/advisories/GHSA-f7xp-22ph-v444)
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-130775 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130775 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-f7xp-22ph-v444
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-130775
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-130775"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lxc/incus · Advisory GHSA-f7xp-22ph-v444
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130775
RecordNVD · CVE-2026-130775

Corrections

None so far.

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

Questions about CVE-2026-130775

Is CVE-2026-130775 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 root can read image objects from projects other than its own, including cached non-public images pulled from authenticated remotes.Source: github.com

Which versions are affected by CVE-2026-130775?

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 when a container has the guest-API image entitlement enabled (security.guestapi.images=true). Administrators can check that setting in each container's configuration.Source: github.com

How do I fix CVE-2026-130775?

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

More CVEs