CVE-2026-100395 · Infrastructure
NO FIX YET
LXC 7.0.0 and earlier, in lxc-copy and the liblxc clone() API, follows attacker-controlled symbolic links when writing /etc/hostname in a copied root filesystem. When root clones an untrusted container without LXC_CLONE_KEEPNAME, an attacker can make the privileged process overwrite an existing host file with the destination container name.
first public Sep 26, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Exposure requires root to clone a container whose source root filesystem is attacker-controlled or less trusted, using lxc-copy or liblxc clone() without LXC_CLONE_KEEPNAME. Unprivileged use and independent cloning implementations are not affected. Hosts that only run their own trusted images or never clone as root can skip it.
Not affected if independent-clone-tooling, trusted-images-only, unprivileged-use
Who cares containers, linux, lxc, self-hosted
lxc-create --version or lxc-info --version; versions 7.0.0 and earlier are in scope.lxc-copy or lxc_container::clone() on container images that are not fully trusted.Unknown from the sources.
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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.