PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-55622 lxc CVE debrief

Incus is a system container and virtual machine manager. Prior to version 7.2.0, missing authorization checks exist for instance copying where an attacker knowing the name of a project that they don't have access to and the name of an instance in that project can copy the instance to a new project. This issue could allow an attacker to access secrets in instances they are not authorized to access.

Vendor
lxc
Product
incus
CVSS
HIGH 7.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-21
Original CVE updated
2026-09-18
Advisory published
2026-08-21
Advisory updated
2026-09-18

Who should care

Defenders responsible for Incus instances, especially those with instance copying enabled, should assess exposure and prioritize patching to prevent unauthorized access to sensitive information.

Why it matters

CVE-2026-55622 is a high-severity vulnerability in Incus that allows unauthorized instance copying, potentially granting access to sensitive information. Defenders should prioritize verifying exposure, restricting access, and upgrading to version 7.2.0 or later.

  • Potential unauthorized access to sensitive information in instances
  • Need to verify exposure to unpatched Incus instances
  • Priority on restricting access to sensitive projects and instances
  • Verification of instance copying restrictions required

Technical summary

Incus versions prior to 7.2.0 have a missing authorization check for instance copying, allowing an attacker with knowledge of a project and instance name to copy the instance to a new project, potentially accessing sensitive information. This issue could allow an attacker to access secrets in instances they are not authorized to access. The vulnerability affects Incus instances with instance copying enabled. Defenders should prioritize verifying exposure to unpatched Incus instances and restrict access to sensitive projects and instances.

Defensive priority

Defenders should prioritize verifying exposure to unpatched Incus instances, especially those with instance copying enabled, and restrict access to sensitive projects and instances.

Recommended defensive actions

  • Verify Incus instance copying is disabled or restricted to authorized users
  • Restrict access to sensitive projects and instances
  • Upgrade to Incus version 7.2.0 or later
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but do not specify which versions are affected or if exploitation has occurred. The vulnerability is in Incus versions prior to 7.2.0. Defenders should verify exposure to unpatched Incus instances, especially those with instance copying enabled. Verification of instance copying restrictions is required. The CVE Program and NVD provide official details, but additional review of source references may be necessary to fully understand the vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-55622 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-55622

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-55622 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-55622

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.