LXD arbitrary file read and write via symlink in container image

Severity: critical · CVSS 9.9 · Published 2026-11-06

LXD is a container management system that allows users to create and run containerized applications. A maliciously crafted container image can exploit insufficient symlink validation to read or write arbitrary files on the host system with root privileges, potentially leading to complete system compromise.

Technologies: github.com/canonical/lxd (Go), Linux Containers LXD. Vendors: Go, Linux Containers.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Critical severity, with a CVSS score of 9.9, published 6 November 2026.
Which products and versions are affected?
github.com/canonical/lxd (Go) < 0.0.0-20260630083100-c5184be310b1, SEMVER:introduced=0,fixed=0.0.0-20260630083100-c5184be310b1.
Is there a fix for This vulnerability?
Yes. github.com/canonical/lxd (Go): upgrade to 0.0.0-20260630083100-c5184be310b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?
It is attacked over the network, in a network appliance.
Am I affected?
Check whether you run github.com/canonical/lxd (Go) or Linux Containers LXD at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/canonical/lxd (Go): upgrade to 0.0.0-20260630083100-c5184be310b1 or later
    go get github.com/canonical/lxd@v0.0.0-20260630083100-c5184be310b1

Technical details

The vulnerability exists in LXD's image validation and extraction logic. When processing a container image, LXD validates the presence of metadata.yaml and a rootfs/ directory entry but fails to sanitize a duplicate top-level rootfs symlink that can be injected into the tar archive during extraction. An attacker can create an image where rootfs points to / (the root filesystem), and when the stopped-container file API opens the rootfs path and chroots to it, the attacker gains root-level access to the host filesystem.

Affected products

  • Linux Containers LXD

Timeline

  • 2026-11-06: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.