{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-63299 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-63299 is a high-severity missing authorization vulnerability in Canonical LXD, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63299 and fix it if it is affected.\n\nWhat it is: CVE-2026-63299 is a high-severity missing authorization vulnerability in Canonical LXD, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63299 in the wild and no public exploit code.\n\nAffected product: Canonical LXD. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63299/ (Markdown: https://insights.sbomify.com/CVE-2026-63299/index.md)","id":"CVE-2026-63299","markdown":"https://insights.sbomify.com/CVE-2026-63299/index.md","name":"CVE-2026-63299","record":{"aliases":["DEBIAN-CVE-2026-63299","GHSA-5h78-p252-989h","UBUNTU-CVE-2026-63299"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"LXD container manager","requires_auth":"low_privilege","summary":"Authenticated users can bypass project disk limits during volume moves or snapshot restores, potentially exhausting storage resources.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"lxd","vendor":"canonical"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"An authorization bypass vulnerability in LXD allows an authenticated user to bypass project-level disk and volume limits. Two related code paths fail to verify resource limits during volume operations: the storagePoolVolumeTypePostMove function omits the limits.AllowVolumeCreation check before moving a volume across projects, and volume snapshot restore operations skip the AllowVolumeUpdate check when the configuration is nil (Config == nil). An attacker can exploit these flaws to allocate storage resources that exceed the administrative limits configured for a project.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Storage volume cross-project move and snapshot restore bypass project disk limits","id":"CVE-2026-63299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-project instance move bypasses all project restrictions allowing host command execution","id":"CVE-2026-63300"},"packages":[],"prev":{"headline":"LXD arbitrary lxc.conf directive injection via NVIDIA instance configuration","id":"CVE-2026-63298"},"products":["LXD"],"published":"2026-08-12","related":[{"cvss_score":9.9,"headline":"Instance template path traversal allows arbitrary host file write as root","id":"CVE-2026-66897","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.9,"headline":"Cross-project cluster migration bypasses project restrictions via cluster notification flag","id":"CVE-2026-62420","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":9.9,"headline":"Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root","id":"CVE-2026-63293","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":9.9,"headline":"Root RCE via image backup.yaml symlink","id":"CVE-2026-63294","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":9.9,"headline":"Project restriction bypass via instance migration config override","id":"CVE-2026-63296","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":9.9,"headline":"Cross-project instance copy bypasses target project restrictions via TOCTOU in config merge","id":"CVE-2026-63297","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":9.9,"headline":"Cross-project instance move bypasses all project restrictions allowing host command execution","id":"CVE-2026-63300","kev_date_added":null,"published":"2026-08-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["Canonical"]},"summary":"Authenticated users can bypass project disk limits during volume moves or snapshot restores, potentially exhausting storage resources.","url":"https://insights.sbomify.com/CVE-2026-63299/"}