Read the docs
TI-2026-85676 Aliases CVE-2026-100395

LXC lxc-copy follows symlinks and overwrites host files

Priority LOW 29CWE-59Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Active
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
None · High · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

LXC 7.0.0 and earlier are affected. The lxc-copy tool and the liblxc clone() API follow symbolic links while updating /etc/hostname in a copied container root filesystem (CWE-59). When root clones a container from an attacker-controlled or less trusted rootfs without LXC_CLONE_KEEPNAME, a planted symlink lets the privileged process truncate and overwrite an existing file outside the destination rootfs with the container name. Unprivileged use is not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

LXC is a userspace interface for the Linux kernel containment features used to create and manage system containers. In LXC 7.0.0 and earlier, lxc-copy and the public liblxc clone() API can follow attacker-controlled symbolic links while updating /etc/hostname in a copied container root filesystem. The affected surfaces are lxc-copy and liblxc's public lxc_container::clone() API. The privileged cloning process must run as root. The source rootfs must be attacker-controlled or less trusted. A symlink can be placed at etc/hostname or in an intermediate component. The clone operation preserves the symlink before updating the hostname. The vulnerable write truncates and overwrites an existing file outside the destination rootfs. When root clones an untrusted container without LXC_CLONE_KEEPNAME, the copied symlink can resolve outside the destination rootfs and cause the privileged process to overwrite an existing host file with the destination container name. Unprivileged use and managers with independent cloning implementations are not affected. LXC_CLONE_KEEPNAME avoids the hostname update and therefore the affected write.

Why it matters now

EPSS 0.00151 4th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
lxclxcup to 7.0.0—No fix listedCNA
  • lxc Vendorlxc Affected up to 7.0.0 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for LXC. Cloning with LXC_CLONE_KEEPNAME avoids the hostname update and the affected write.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-11-05 Threatist record created from CVE-2026-100395
  2. 2026-11-06 Affected versions changed · Red Hat
  3. 2026-11-06 CVSS score added · Red Hat
  4. 2026-11-07 Priority changed: MEDIUM → LOW

References

  • TI-2019-04061 runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows… CVSS 3.1HIGH 8.6
  • TI-2026-45063 Incus vulnerable to root RCE via image backup.yaml symlink CVSS 3.1CRITICAL 9.9
  • TI-2026-44978 Incus: Cross-project instance copy bypasses target project restrictions via TOCTOU in config merge CVSS 3.1CRITICAL 9.9
  • TI-2026-36039 Incus has an arbitrary file write on its client due to trusted image hash CVSS 3.1CRITICAL 9.9
  • TI-2026-36024 Incus has an arbitrary file write via path traversal in S3 multipart upload CVSS 3.1CRITICAL 9.9
  • TI-2026-36022 Incus has a restricted project bypass leading to arbitrary command execution CVSS 3.1CRITICAL 9.9
See all 63 →

Sources