CVE-2026-63295

Awaiting Analysis Awaiting Analysis - Queue

Authorization Bypass in LXD Container Isolation

Publication date: 2026-08-12

Last updated on: 2026-08-28

Assigner: Canonical Ltd.

Description

An authorization bypass vulnerability in LXD allows an authenticated attacker to bypass project-level container isolation restrictions. When a project is configured with restrictions on container privileges (such as enforcing restricted.containers.privilege=isolated), LXD fails to enforce the requirement if an instance configuration omits the security.idmap.isolated key. An attacker can exploit this flaw by creating or updating an instance without explicitly setting security.idmap.isolated, bypassing the target project's security constraints.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-12

Last Modified

2026-08-28

Generated

2026-09-02

AI Q&A

2026-08-13

EPSS Evaluated

2026-08-31

NVD

CVE-2026-63295

EUVD

EUVD-2026-57516

Affected Vendors & Products

Vendor	Product	Version / Range
canonical	lxd	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-863	The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

Executive Summary

CVE-2026-63295 is an authorization bypass in LXD where an authenticated attacker can bypass project-level container isolation restrictions. When a project enforces restricted.containers.privilege=isolated, LXD fails to enforce it if an instance configuration omits the security.idmap.isolated key. Attackers exploit this by creating or updating instances without setting security.idmap.isolated, bypassing security constraints.

Detection Guidance

To detect this vulnerability, check LXD instances in projects with restricted.containers.privilege=isolated for missing security.idmap.isolated configurations. Use commands like 'lxc list --project <project_name>' to list instances and 'lxc config show <instance_name> --project <project_name>' to verify security.idmap.isolated settings.

Impact Analysis

This vulnerability allows attackers to bypass intended container isolation, potentially leading to denial of service, data integrity issues, or confidentiality breaches between co-tenant containers. It enables unauthorized access or interference with other containers in the same project.

Compliance Impact

This vulnerability could violate compliance requirements that mandate strict tenant isolation, such as GDPR's data separation principles or HIPAA's access controls. Failure to enforce isolation may result in unauthorized data exposure or integrity violations, posing legal and regulatory risks.

Mitigation Strategies

Immediately update LXD to the latest patched version. For existing instances, ensure security.idmap.isolated=true is explicitly set in restricted projects. Review all projects with restricted.containers.privilege=isolated and update configurations to enforce isolation.

Hi! I’m here to help you understand CVE-2026-63295. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70