Skip to content
Fencer Intel
medium 4.3

CVE-2026-63295 json

Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`

published 3mo ago modified 18d ago also EUVD-2026-57516 , GHSA-7vp9-3vmp-c5jm

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository canonical/lxd. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

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.

Patch / fix

  • Canonical LXD 4.0.12, 5.0.8, 5.21.6, 6.10
  • lxd openSUSE Leap 16.0 5.21.6-bp160.1.1

opensuse advisories openSUSE-SU-2026:21788-1

Is CVE-2026-63295 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/canonical/lxd/security/advisories/GHSA-7vp9-3vmp-c5jm referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Affected products

  • Canonical LXD

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of canonical/lxd published their own advisory on GitHub. Reviewed sources take precedence over it.