Incus versions prior to 7.6.0 contain a configuration injection vulnerability that allows users who can launch instances from controlled images to inject LXC directives by embedding line breaks in certain OCI configuration values. This can enable attackers to execute commands as root on the host or bind-mount host paths, even from restricted projects. The vulnerability is fixed in version 7.6.0.
Incus from 7.3.0 before 7.6.0 contains an authentication bypass vulnerability in the /dev/incus guest API that allows a process in one container to impersonate another by creating a cgroup named with a forged lxc.monitor. component. Attackers can read the target container's user.* and cloud-init.* configuration and devices, subscribe to its events, mark it ready, and export images across projects.
Incus versions prior to 7.6.0 have an authorization bypass vulnerability that allows restricted clients to create and access default project resources improperly. This flaw enables attackers to create bridge networks with malicious raw.dnsmasq directives, potentially leading to remote code execution as root on the host system. The vulnerability arises from improper entitlement checks on the requested project parameter, allowing manipulation of inherited resources. The issue is fixed in version 7.6.0.
Incus versions prior to 7.6.0 have a vulnerability that exposes sensitive certificate and cluster join token secrets via the default project event stream. Additionally, the system skips authorization checks when cancelling operations without associated permissions. This allows restricted clients to subscribe to operation events, capture certificate tokens, enroll unrestricted certificates, and gain full server access or cancel token operations by UUID.
Incus versions prior to 7.6.0 have an improper authorization vulnerability that allows restricted and view-only clients to access default project resources directly. This flaw enables attackers who know resource names to read sensitive data such as profiles, images, network zone peer keys, stored credentials, and export backups containing full contents or S3 admin keys. The vulnerability is fixed in version 7.6.0.
Incus before 7.6.0 contains a resource exhaustion vulnerability in the storage bucket S3 listener, which buffers entire signed request bodies in memory before verifying the signature or credential role. Attackers knowing only a valid access key, or holding a read-only credential, can send many concurrent large requests to exhaust daemon memory.
Incus versions prior to 7.6.0 contain a critical path traversal vulnerability that allows malicious migration peers to write files outside intended directories. This occurs when unvalidated dependent volume and snapshot names are supplied in the migration offer header. Exploitation can lead to creation of root-owned volumes with attacker-controlled content at arbitrary host paths, compromising hosts using directory storage pools, bypassing storage pool access restrictions, or causing daemon crashes. The vulnerability is fixed in version 7.6.0.
Incus versions prior to 7.6.0 contain a path traversal vulnerability that allows users with permission to import custom volumes to exploit unvalidated snapshot names. Crafted backups with traversal sequences in snapshot names can cause deletion operations to remove arbitrary directories on the host as root, and renaming or mounting operations to affect arbitrary paths.
Incus versions before 7.6.0 have an information disclosure vulnerability allowing clients with project event-view access to read migration websocket secrets. This flaw enables attackers to hijack in-flight migration control and filesystem websockets before the legitimate peer, potentially exposing instance configuration and filesystem data. The vulnerability is fixed in version 7.6.0.
Incus before 7.6.0 contains an information disclosure vulnerability that allows project-restricted authenticated clients to receive other projects' OVN ACL logs because these events are broadcast with an empty project. Attackers can subscribe to network-acl events on one accessible project to observe internal IPs, ports, protocols, and allow/drop decisions across all projects.
Incus versions prior to 7.6.0 contain an authentication bypass vulnerability that allows remote attackers to impersonate any trusted certificate by appending its public certificate to their TLS client chain. This flaw enables attackers to gain unauthorized cluster-level access, bypass authorization controls, modify trust store entries, and affect scriptlet-based authorization decisions. The vulnerability is fixed in version 7.6.0.
Incus versions prior to 7.6.0 have an authorization bypass vulnerability in the guest-API image export handler. This flaw allows container root users with the guest-API image entitlement to export images from projects other than their own by manipulating the project query parameter. This includes access to non-public images pulled from authenticated remotes. The issue is fixed in version 7.6.0.
Incus versions prior to 7.6.0 contain a critical privilege escalation vulnerability. Rebuilding a never-started unprivileged container causes it to boot without a user namespace, resulting in root processes inside the container running as host uid 0. These processes retain powerful capabilities such as sys_module and lack device cgroup restrictions, allowing them to load kernel modules and potentially compromise the host system.
Incus before 7.6.0 contains an authorization bypass that allows restricted project users to create resources in the unrestricted default project by targeting projects lacking features.* flags. Attackers can create bridge networks with raw.dnsmasq dhcp-script injection to run scripts as root, or custom volumes with block.create_options mkfs arguments to read host files.
Incus versions prior to 7.6.0 have an improper authorization vulnerability that allows restricted TLS clients to access other projects' bucket S3 keys and profile configurations. By using recursive bucket listing or querying profiles with all-projects enabled, attackers can retrieve sensitive credentials and environment data across projects.
Incus versions prior to 7.6.0 create NBD servers for VM migration and disk export on abstract unix sockets without permission checks. These socket names are visible in /proc/net/unix, allowing a local unprivileged user to connect during an operation and read or modify the VM disk. This can lead to code execution within the guest VM on the migration's receiving side. The vulnerability is fixed in Incus 7.6.0.
CVE-2026-130771 is a vulnerability in Incus before version 7.6.0 where improper handling of special files, hard links, or symlinks in backup or image metadata allows restricted project users to read or overwrite host files. This flaw enables attackers to import crafted backups with malicious device nodes, hard-linked backup.yaml files, or symlinks, potentially corrupting host storage, overwriting files, or leaking data from other projects.
Incus before 7.6.0 contains a denial of service vulnerability that allows clients permitted to create instances to crash the daemon by importing a backup with a null snapshot entry in index.yaml. Attackers can trigger an unrecovered nil pointer dereference during configuration rewrite, terminating the daemon and all containers and virtual machines on the node.
CVE-2026-115378 is an arbitrary file write vulnerability in the incus component of lxc. It affects versions before 6.0.7, versions 6.1.0 up to but not including 7.0.2, and versions 7.1.0 up to but not including 7.5.0. The flaw exists in the sftpRecursivePullFile function, where a malicious incus-agent with root privileges inside a virtual machine can escape the intended target directory during a recursive file pull operation. This allows writing attacker-controlled files on the host, including sensitive files like /etc/shadow. The vulnerability has a CVSS 4.0 base score of 6.9, indicating medium severity. Fixes are available in versions 6.0.7, 7.0.2, and 7.5.0.
CVE-2026-115377 is a critical arbitrary file write vulnerability in Incus (lxc) affecting versions before 6.0.7, 7.0.2, and 7.5.0. It allows malicious migration sources to write files on the host by planting symbolic links in transferred volumes. This can lead to full host compromise by writing files as root.