CVE-2026-115376 lxc CVE debrief

Who should care

Defenders responsible for Incus deployments, especially those with project-restricted clients, should assess exposure and verify custom volume copy configurations. They should also review and update Incus versions to 7.0.2 or 7.5.0, or later, and monitor for suspicious activity related to custom volume copies. Additionally, defenders should consider the potential operational impacts of this vulnerability, including potential unauthorized access to project,

Why it matters

CVE-2026-115376 is a high-severity authorization bypass vulnerability in Incus that allows project-restricted clients to copy volumes, potentially leading to unauthorized access and disruption of project operations. Defenders should prioritize verifying exposure and updating vulnerable Incus versions.

• Potential unauthorized access to sensitive project data
• Possible disruption of project operations due to volume copy manipulation
• Need for verification of Incus version and configuration
• Potential for lateral movement within Incus deployments

Technical summary

Incus versions 7.0.1 before 7.0.2 and 7.2.0 before 7.5.0 contain an authorization bypass vulnerability that allows project-restricted clients to copy volumes by omitting source.type. Attackers can send crafted POST requests to the custom volumes endpoint with a chosen source.project to copy and read other projects' volumes, snapshots, and configuration. This vulnerability can lead to unauthorized access and disruption of project operations. Defenders should prioritize verifying exposure in Incus deployments, especially for project-restricted clients, and review custom volume copy configurations.

Defensive priority

Defenders should prioritize verifying exposure in Incus deployments, especially for project-restricted clients, and review custom volume copy configurations.

Recommended defensive actions

• Verify Incus deployments for project-restricted clients and custom volume copy configurations
• Review and update Incus versions to 7.0.2 or 7.5.0, or later
• Monitor for suspicious activity related to custom volume copies
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the authorization bypass vulnerability in Incus versions 7.0.1 before 7.0.2 and 7.2.0 before 7.5.0. Official sources include the CVE Program record, NVD vulnerability detail, and vendor advisories.

Sources and 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.