Skip to content
Fencer Intel
critical 9.9

CVE-2026-63298 json

LXD arbitrary lxc.conf directive injection via NVIDIA instance configuration

published 3mo ago modified 18d ago also EUVD-2026-57511 , GHSA-vfh7-q59q-54v2

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
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

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.

Patch / fix

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

opensuse advisories openSUSE-SU-2026:21788-1

Is CVE-2026-63298 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
total
Assessed
2mo ago

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/canonical/lxd/security/advisories/GHSA-vfh7-q59q-54v2 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • Canonical LXD

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

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.