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.
Incus versions 7.0.1 before 7.0.2 and 7.2.0 before 7.5.0 have an authorization bypass vulnerability. This flaw allows project-restricted clients to copy volumes by omitting the source.type parameter. Attackers can craft POST requests to the custom volumes endpoint specifying a source.project to access and copy volumes, snapshots, and configurations from other projects.
Incus versions 7.0.0 before 7.0.2 and 7.1.0 before 7.5.0 contain a critical path traversal vulnerability. This flaw allows clients with instance creation privileges to write files on the host by importing crafted instance backups with malicious dependent volume names. Exploitation can lead to creation of root-owned directories with attacker-controlled content, resulting in full host compromise. The vulnerability is fixed in versions 7.0.2 and 7.5.0.
Incus versions 7.0.0 before 7.0.2 and 7.1.0 before 7.5.0 have a cryptographic signature verification flaw in their built-in S3 server. This flaw allows holders of presigned URLs to inject unsigned x-amz-* headers, including an X-Amz-Copy-Source header, enabling them to copy other bucket objects onto the granted key. This can lead to unauthorized disclosure of object contents and ETags.
CVE-2026-115373 is a missing authorization vulnerability in the Incus container management system affecting versions before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0. It allows project-restricted clients to access operations from other projects via the GET /1.0/operations/{uuid} endpoint. Exploitation requires knowledge of a valid operation UUID and possession of a restricted certificate. Sensitive information such as command lines, environment secrets, websocket secrets, and trust enrolment tokens can be retrieved by attackers.
Incus versions from 7.3.0 up to but not including 7.5.0 contain a vulnerability that allows restricted project users to bypass project restrictions. This flaw enables attackers to set the block.create_options parameter via volume update, copy, and move operations. By exploiting this, an attacker can inject arguments into the mkfs command executed as root, potentially leading to privilege escalation. The issue is fixed in version 7.5.0.
Incus versions 6.0.3 before 6.0.7, 6.6.0 before 7.0.2, and 7.1.0 before 7.5.0 contain an improper authorization vulnerability. This flaw allows restricted TLS clients to access storage bucket keys in the default project. Exploiting this, attackers can retrieve S3 access and secret keys, enabling them to read, modify, or delete objects in those buckets. The vulnerability has a high severity with a CVSS score of 7.1. Fixed versions are 6.0.7, 7.0.2, and 7.5.0.
CVE-2026-115370 is a restriction bypass vulnerability in Incus versions 6.0.5 before 6.0.7, 6.12.0 before 7.0.2, and 7.1.0 before 7.5.0. It allows restricted project users with instance creation rights to send refresh migration requests that cause the server to open outbound TLS websocket connections and probe reachable services. This could lead to unauthorized network probing via the server.
CVE-2026-62941 is a critical authorization vulnerability in incus, a system container and virtual machine manager. Prior to version 7.3.0, when copying an instance across projects, the project restriction check occurs before the source instance's configuration is merged. This allows dangerous configuration keys to bypass project restrictions. The issue is patched in version 7.3.0.
A missing authorization vulnerability in Incus (a system container and VM manager) prior to version 7.3.0 allows restricted project users to escalate privileges during instance migration by applying user-supplied configuration overrides without enforcing project restrictions. This can lead to privileged container creation and host escape. The issue is fixed in version 7.3.0.
CVE-2026-62867 is a critical vulnerability in Incus, a system container and virtual machine manager. Prior to version 7.3.0, improper validation of user-supplied 'block.create_options' in storage volume configuration allows argument injection in the filesystem creation command line. This flaw enables a project-scoped user to inject arbitrary arguments into a root-executed binary. The issue is patched in version 7.3.0.
CVE-2026-62313 is an authorization vulnerability in Incus, a system container and virtual machine manager. Prior to version 7.3.0, the project-level enforcement of the 'restricted.containers.privilege=isolated' setting can be bypassed. This allows users to create containers that share the host's uid/gid map, defeating the intended isolation between containers and weakening security boundaries. The issue arises because the enforcement only rejects an explicitly set 'security.idmap.isolated=false' but does not enforce restrictions when the key is omitted, which defaults to non-isolation. Version 7.3.0 includes a patch for this vulnerability.
CVE-2026-47753 is a NULL pointer dereference vulnerability in the Incus system container and virtual machine manager prior to version 7.1.0. An authenticated user with permission to create instances can trigger a daemon crash by uploading a crafted backup tarball, causing denial of service across all projects on the affected cluster member. The issue arises from a missing null check on the Volume field in the instance-import path. Version 7.1.0 includes a patch that addresses this vulnerability.
Incus is a system container and virtual machine manager. Prior to version 7.3.0, a malicious image containing a `metadata.yaml` symlink pointing to an arbitrary host path allows an authenticated Incus user to read or overwrite any file on the host as root via the instance metadata API. The `exec-output` and `templates/` paths were patched in a prior release using `Lstat` rejection and `os.OpenRoot` confinement; `metadata.yaml` was not included in either patch and remains exploitable. Version 7.3.0 patches the issue.
Incus is a system container and virtual machine manager. Prior to version 7.3.0, an unprivileged, project-confined Incus user (a non-admin TLS/RBAC identity with `can_create_images` and `can_create_instances`) can execute arbitrary code as root on the host. A crafted image ships `backup.yaml` as a symlink to a host file. When the root daemon writes the instance's backup file, it follows the symlink. Version 7.3.0 patches the issue.
Incus, a system container and virtual machine manager, has an improper access control vulnerability prior to version 7.2.0. This flaw allows an attacker who knows the name of a project and an instance within that project, without having authorization, to copy the instance to a new project. Exploiting this vulnerability could enable unauthorized access to secrets stored in instances. The issue is patched in version 7.2.0.
CVE-2026-55621 is an improper access control vulnerability in the Incus container and virtual machine manager prior to version 7.2.0. The flaw allows an attacker who knows the name of a project and a custom volume within it, but lacks authorization, to copy that volume to a new project. This can lead to unauthorized access to secrets stored in custom volumes. The issue is patched in version 7.2.0.
Incus is a system container and virtual machine manager. Prior to version 7.0.0, uploads of large amount of data by authenticated users can run the Incus server out of disk space, potentially taking down the host system. The impact here is limited for anyone using storage.images_volume and storage.backups_volume as those users will have large uploads be stored on those volumes rather than directly on the host filesystem. This is the default behavior on IncusOS. This issue has been patched in version 7.0.0.
Incus is a system container and virtual machine manager. Prior to version 7.0.0, backup.GetInfo() trusts the inline backup/index.yaml config when present and only falls back to parsing the legacy backup/container/backup.yaml file if result.Config == nil. As a result, an archive can carry a valid inline config that passes the initial import preflight while also carrying a malformed legacy backup/container/backup.yaml file that is reparsed later from the restored file system. ParseConfigYamlFile() accepts YAML documents with no container section, and multiple downstream consumers then dereference. Container without checking for nil. Confirmed examples in the instance restore and import flow include backup.UpdateInstanceConfig() and internalImportFromBackup(). An authenticated user with permission to import instance backups may be able to crash the Incus daemon with a crafted backup archive whose inline backup/index.yaml is valid but whose extracted legacy backup.yaml omits container. The crash occurs in the restore path after archive extraction has begun. This issue has been patched in version 7.0.0.