{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63298 exists.","fix":"Apply the vendor's patch.","what":"CVE-2026-63298 is a high-severity command injection 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-63298 and fix it if it is affected.\n\nWhat it is: CVE-2026-63298 is a high-severity command injection 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63298 exists.\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-63298/ (Markdown: https://insights.sbomify.com/CVE-2026-63298/index.md)","id":"CVE-2026-63298","markdown":"https://insights.sbomify.com/CVE-2026-63298/index.md","name":"CVE-2026-63298","record":{"aliases":["DEBIAN-CVE-2026-63298","GHSA-vfh7-q59q-54v2","UBUNTU-CVE-2026-63298"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"LXD container manager","requires_auth":"low_privilege","summary":"Authenticated attackers can inject arbitrary directives into LXD configuration files via NVIDIA settings, leading to arbitrary code execution on the host.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"lxd","vendor":"canonical"}],"cvss":{"score":8.7,"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-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"An improper neutralization of special elements vulnerability in LXD's NVIDIA instance configuration handling allows an authenticated attacker to inject arbitrary configuration directives. By supplying newline characters within the 'nvidia.driver.capabilities' or 'nvidia.require.*' configuration values, an attacker can manipulate the generated lxc.conf file. This flaw enables the attacker to execute arbitrary code on the host system with the privileges of the LXD daemon.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"LXD arbitrary lxc.conf directive injection via NVIDIA instance configuration","id":"CVE-2026-63298","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Storage volume cross-project move and snapshot restore bypass project disk limits","id":"CVE-2026-63299"},"packages":[],"prev":{"headline":"Cross-project instance copy bypasses target project restrictions via TOCTOU in config merge","id":"CVE-2026-63297"},"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["Canonical"]},"summary":"Authenticated attackers can inject arbitrary directives into LXD configuration files via NVIDIA settings, leading to arbitrary code execution on the host.","url":"https://insights.sbomify.com/CVE-2026-63298/"}