Skip to content
Cloud

CVE-2026-66897

9.9
Critical
EPSS 0.67%Patch availableAug 24, 2026

LXD template path traversal lets container users overwrite host files and gain root.

common questions

Is CVE-2026-66897 being exploited?

Not confirmed. CVE-2026-66897 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.67% probability of exploitation in the next 30 days.

How severe is CVE-2026-66897?

CVE-2026-66897 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-66897?

Yes. A fix has been recorded for CVE-2026-66897. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-66897 affect?

CVE-2026-66897 affects Canonical LXD, Linux hosts running LXD, Containers/images launched via LXD. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-66897?

Restrict container edit/image launch privileges, isolate LXD hosts, and apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Canonical LXDLinux hosts running LXDContainers/images launched via LXD
impact

Path traversal in LXD template handling allows attackers to overwrite root-owned host files and achieve host root code execution via crafted images or container edits.

action required

Immediate action required

affected versions
Canonical LXD
  • affected>= 4.0.0 and < 4.0.13
  • affected>= 5.0.0 and < 5.0.9
  • affected>= 5.21.0 and < 5.21.7
  • affected>= 6.0 and < 6.10

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free