CVE-2026-63298
Authenticated LXD NVIDIA config injection leads to host code execution as LXD daemon.
Is CVE-2026-63298 being exploited?
Not confirmed. CVE-2026-63298 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-63298?
CVE-2026-63298 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63298?
Yes. A fix has been recorded for CVE-2026-63298. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63298 affect?
CVE-2026-63298 affects LXD daemon, lxc.conf generation, nvidia.driver.capabilities, nvidia.require.*, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63298?
Apply vendor patch ASAP; restrict LXD daemon access and sanitize/deny untrusted NVIDIA config values.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker injects newline into nvidia.* config to tamper lxc.conf and execute code on the host with LXD daemon privileges.
Immediate action required
- affected>= 5.0.0 and < 5.0.8
- affected>= 5.21.0 and < 5.21.6
- affected>= 4.0.0 and < 4.0.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.