Description Summary:
An authenticated Incus user can read or overwrite arbitrary files on the host as root by using a crafted image with a symlink in the metadata.yaml file.

Executive Summary:
A critical file system vulnerability in LXC Incus enables an authenticated user to perform arbitrary file reads or writes on the host system with root privileges.

Vulnerability Details

CVE-ID: CVE-2026-63343

Affected Software: LXC Incus

Affected Versions: < 7.3.0

Vulnerability: This vulnerability arises from insufficient validation of symbolic links within the metadata.yaml file of container images. An authenticated user can exploit this to manipulate files on the host, as the system fails to confine these operations correctly.

Business Impact

Successful exploitation grants an attacker the power to overwrite critical system binaries, inject malicious configuration files, or steal sensitive data from the host. This effectively breaks the security boundary between the container and the underlying host operating system. With a CVSS score of 9.9, this vulnerability poses a severe threat to the entire infrastructure managed by the affected software.

Remediation Plan

Immediate Action: Update LXC Incus to version 7.3.0 or later to patch the metadata handling logic.

Proactive Monitoring: Review system logs for unexpected file access patterns or modifications to sensitive directories occurring via the Incus metadata API.

Compensating Controls: Implement strict file system monitoring and integrity checks on the host to detect unauthorized modifications to system files.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 21, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is highly exploitable for any authenticated user with access to the instance metadata API.

Analyst Recommendation

Given the potential for full host system compromise, upgrading to version 7.3.0 is mandatory. Security teams should ensure that all Incus installations are updated without delay to prevent unauthorized host file access.

Description Summary:
An authenticated Incus user can achieve arbitrary code execution as root on the host by supplying a crafted image containing a symlink to a host file.

Executive Summary:
A critical vulnerability in LXC Incus allows an authenticated, project-confined user to escape their container environment and execute arbitrary code as root on the host system.

Vulnerability Details

CVE-ID: CVE-2026-63125

Affected Software: LXC Incus

Affected Versions: < 7.3.0

Vulnerability: This vulnerability involves improper link resolution, where the root daemon follows a symbolic link placed in a backup.yaml file within a crafted image. An authenticated user with limited privileges can leverage this flaw to perform unauthorized file operations on the host.

Business Impact

The ability for a low-privileged user to gain root execution on the host represents a total compromise of the virtualization infrastructure. This allows an attacker to bypass all container isolation boundaries, potentially leading to complete data loss, unauthorized access to sensitive host configurations, and the installation of persistent backdoors. Given the CVSS score of 9.9, the risk to confidentiality, integrity, and availability is extreme.

Remediation Plan

Immediate Action: Update all instances of LXC Incus to version 7.3.0 or later immediately to resolve the symlink following flaw.

Proactive Monitoring: Audit Incus logs for unusual image creation activity or unauthorized access attempts originating from non-admin project-confined identities.

Compensating Controls: Strictly enforce role-based access control policies to limit the number of users capable of creating images until the update is deployed.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 21, 2026, there is no confirmed active exploitation in the wild: however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is inherently dangerous because it directly targets the container manager's trust relationship with files provided by users.

Analyst Recommendation

The severity of this vulnerability necessitates immediate patching. Organizations should prioritize updating their Incus environments to 7.3.0 to neutralize the risk of host-level system compromise.

Description Summary:
Incus versions prior to 7.3.0 contain an authorization flaw where instance configuration is merged before project restriction checks, allowing security bypasses during instance copying.

Executive Summary:
A critical authorization flaw in lxc Incus allows authenticated users to bypass security restrictions by injecting malicious configuration keys during cross-project instance copying.

Vulnerability Details

CVE-ID: CVE-2026-62941

Affected Software: lxc Incus

Affected Versions: < 7.3.0

Vulnerability: The vulnerability occurs because the system performs the authorization check before merging the source instance configuration. An authenticated user can exploit this race-like condition in logic to introduce dangerous configuration keys that would otherwise be rejected by the target project's security policy.

Business Impact

By bypassing project restrictions, an attacker can deploy privileged containers or utilize sensitive configuration keys to escape the container environment. The CVSS score of 9.9 reflects the total impact on confidentiality, integrity, and availability, posing a significant risk to any organization relying on Incus for workload isolation.

Remediation Plan

Immediate Action: Update lxc Incus to version 7.3.0 or later to ensure that security configuration checks are performed after merging instance definitions.

Proactive Monitoring: Review audit logs for unusual instance creation or copy events that involve sensitive configuration keys.

Compensating Controls: Implement strict Role-Based Access Control (RBAC) to limit the ability of users to perform cross-project instance operations until the patch is deployed.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 21, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly exploitable for any authenticated user with access to project operations.

Analyst Recommendation

Given the existence of a proof-of-concept and the critical nature of this authorization bypass, immediate patching is required. Administrators should prioritize this update to prevent unauthorized privilege escalation and maintain the security boundaries of their containerized environments.

Description Summary:
Incus versions prior to 7.3.0 fail to enforce project restrictions during instance migration, allowing restricted users to escalate privileges and escape to the host.

Executive Summary:
A critical authorization bypass in lxc Incus enables restricted project users to elevate privileges and escape container isolation during instance migration.

Vulnerability Details

CVE-ID: CVE-2026-62940

Affected Software: lxc Incus

Affected Versions: < 7.3.0

Vulnerability: This is a missing authorization vulnerability where project-specific security restrictions are ignored during the migration of instances. An authenticated user can supply unauthorized configuration overrides, such as privileged security flags, to escalate their container status.

Business Impact

This flaw effectively nullifies the multi-tenancy security model of the Incus platform. With a CVSS score of 9.9, the impact is total, as it allows an attacker to bypass project boundaries and gain privileged access to the host system, leading to full infrastructure compromise.

Remediation Plan

Immediate Action: Apply the update to lxc Incus version 7.3.0 or later across all cluster members to enforce mandatory project restriction checks.

Proactive Monitoring: Monitor cluster migration logs for any configuration overrides that appear suspicious or originate from non-privileged project accounts.

Compensating Controls: Limit migration permissions to authorized administrative personnel only until the software update is applied to all nodes in the cluster.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 21, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is highly critical because it directly targets the core isolation mechanisms of the container manager.

Analyst Recommendation

The ability to bypass project restrictions and achieve host escape is a catastrophic security failure. Organizations using Incus in multi-tenant environments must treat this as a high-priority patching task to maintain system integrity.

Description Summary:
Incus versions prior to 7.3.0 are vulnerable to argument injection in storage volume configuration, allowing project-scoped users to execute arbitrary commands as root on the host.

Executive Summary:
A critical argument injection vulnerability in lxc Incus allows authenticated project users to achieve root execution on the underlying host.

Vulnerability Details

CVE-ID: CVE-2026-62867

Affected Software: lxc Incus

Affected Versions: < 7.3.0

Vulnerability: The vulnerability stems from improper validation of user-provided configuration options within storage volumes. This allows an authenticated user with project-level access to inject malicious arguments into commands executed by the system with root privileges.

Business Impact

Successful exploitation allows an attacker to break out of their restricted project environment and gain full administrative control over the host system. Given the CVSS score of 9.9, this vulnerability represents an extreme risk to infrastructure integrity, as it facilitates complete system compromise and potential lateral movement within the network.

Remediation Plan

Immediate Action: Upgrade lxc Incus to version 7.3.0 or later immediately to apply the necessary input validation patches.

Proactive Monitoring: Audit system logs for unexpected binary executions or unusual command-line arguments initiated by the Incus service user.

Compensating Controls: Restrict project access to only highly trusted users until the software can be patched, and ensure that the host OS is hardened against container breakout techniques.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 21, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the potential for root-level command execution from a restricted user context.

Analyst Recommendation

This vulnerability presents a severe risk to host security and multi-tenant isolation. Administrators must prioritize updating to version 7.3.0 to neutralize this command injection vector and prevent unauthorized root access.

Description Summary:
LXC Incus versions prior to 7.2.0 are vulnerable to an improper access control issue, potentially allowing authenticated users to manipulate the system environment.

Executive Summary:
A high-severity access control vulnerability in LXC Incus, for which a proof-of-concept exists, allows authenticated users to bypass security restrictions.

Vulnerability Details

CVE-ID: CVE-2026-55622

Affected Software: LXC Incus

Affected Versions: < 7.2.0

Vulnerability: This vulnerability involves improper access control (CWE-284) within the Incus management framework. It allows an authenticated user with low-level privileges (PR:L) to perform unauthorized operations, potentially impacting the confidentiality and integrity of containerized workloads.

Business Impact

The ability for an authenticated user to bypass access controls can lead to unauthorized modification of container settings or exposure of sensitive environment data. Given the CVSS score of 7.7, this vulnerability poses a high risk to the overall stability and security of the virtualized infrastructure.

Remediation Plan

Immediate Action: Apply the vendor-supplied security update by upgrading Incus to version 7.2.0 or later.

Proactive Monitoring: Monitor system logs for unusual container deployment or configuration changes that deviate from established operational baselines.

Compensating Controls: Enforce the principle of least privilege for all users who interact with the Incus management interface and limit access to the network management port.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 23, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The existence of a proof-of-concept increases the likelihood of potential weaponization.

Analyst Recommendation

Given the existence of a proof-of-concept, the urgency to patch this vulnerability is elevated. Organizations should prioritize updating to version 7.2.0 to mitigate the risk of unauthorized access and potential system compromise.

Description Summary:
LXC Incus versions prior to 7.2.0 contain an improper access control vulnerability that may allow authenticated users to perform unauthorized actions.

Executive Summary:
A high-severity access control vulnerability in LXC Incus allows authenticated users to bypass intended security restrictions, threatening system and container integrity.

Vulnerability Details

CVE-ID: CVE-2026-55621

Affected Software: LXC Incus

Affected Versions: < 7.2.0

Vulnerability: This is an improper access control vulnerability (CWE-284) that allows an authenticated user to perform actions outside their intended scope. The vulnerability requires low privileges (PR:L) and is exploitable over the network (AV:N).

Business Impact

Successful exploitation allows for unauthorized interaction with the container management environment, which could lead to resource compromise or unauthorized configuration changes. With a CVSS score of 7.7, this issue presents a significant risk to the security posture of the infrastructure hosting these containers.

Remediation Plan

Immediate Action: Upgrade all instances of LXC Incus to version 7.2.0 or later as directed by the vendor advisory.

Proactive Monitoring: Review audit logs for suspicious container management activity or unauthorized API calls originating from authenticated user sessions.

Compensating Controls: Restrict network access to the Incus management interface to trusted administrative subnets until the software can be patched.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 23, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherent to the access control logic, necessitating prompt patching.

Analyst Recommendation

Due to the severity of access control flaws in container management systems, immediate remediation is required. Administrators must update to version 7.2.0 to ensure that standard user privileges are strictly enforced.

Description Summary:
Incus client versions before 7.2.0 are vulnerable to an arbitrary file write flaw when processing a malicious Incus-Image-Hash header from an image server, potentially leading to root-level code execution.

Executive Summary:
A critical vulnerability in the Incus client allows a malicious image server to execute arbitrary code with root privileges on the client system.

Vulnerability Details

CVE-ID: CVE-2026-48769

Affected Software: lxc incus

Affected Versions: < 7.2.0

Vulnerability: This is an input validation vulnerability (CWE-20) in the Incus client. An attacker controlling an image server can supply a crafted Incus-Image-Hash header to trigger an arbitrary file write on the client machine, which can be leveraged to gain root-level command execution.

Business Impact

This vulnerability carries a CVSS score of 9.9, indicating an extreme risk to any environment that consumes images from potentially untrusted or compromised servers. Successful exploitation results in full control over the client system, including root access, which could lead to complete data breach or infrastructure takeover.

Remediation Plan

Immediate Action: Update the Incus client to version 7.2.0 or later to patch the header validation logic.

Proactive Monitoring: Monitor client-side logs for unexpected file system activities or unauthorized processes running with root permissions following image import operations.

Compensating Controls: Only pull images from trusted, verified, and internal image repositories to mitigate the risk of interacting with a malicious server.

Exploitation Status

Public Exploit Available: Unknown (no confirmed public weaponized exploit was identified in the provided sources).

Analyst Notes: As of August 21, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The ability to gain root access via a malicious image source makes this a very dangerous vector for supply chain attacks.

Analyst Recommendation

The severity of this vulnerability, combined with the documented existence of a proof-of-concept, necessitates immediate action. All Incus clients should be updated to version 7.2.0 to remediate this critical flaw and prevent potential root-level escalation.

Description Summary:
Incus versions prior to 7.2.0 contain an argument injection vulnerability due to improper validation of backup compression algorithm inputs, enabling arbitrary file writes on the host.

Executive Summary:
An improper input validation flaw in lxc Incus allows authenticated users to perform arbitrary file writes on the host, potentially leading to full system compromise.

Vulnerability Details

CVE-ID: CVE-2026-48755

Affected Software: lxc incus

Affected Versions: < 7.2.0

Vulnerability: This is an input validation vulnerability (CWE-20) that occurs during the processing of backup compression algorithms. An attacker with low-level privileges can inject arbitrary arguments into the command line, resulting in file writes on the host system.

Business Impact

With a CVSS score of 9.9, this vulnerability represents a significant risk to containerized environments. By allowing arbitrary file writes on the host, an attacker can escalate privileges or gain persistent access to the underlying infrastructure, undermining the isolation boundary provided by Incus. This poses a high risk to both the confidentiality and integrity of the host server.

Remediation Plan

Immediate Action: Upgrade the Incus software to version 7.2.0 or later to ensure the proper validation of input arguments.

Proactive Monitoring: Review system logs for unusual command line executions or unauthorized file modifications in sensitive host directories.

Compensating Controls: Restrict access to the Incus administrative interface to trusted users only and employ strict container security policies to limit host-level interactions.

Exploitation Status

Public Exploit Available: Unknown (no confirmed public weaponized exploit was identified in the provided sources).

Analyst Notes: As of August 21, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While exploitation requires authenticated access, the ability to escape the container context makes this a high-priority security issue.

Analyst Recommendation

Organizations utilizing Incus should treat this as a high-priority update. Administrators must verify their current version and apply the 7.2.0 patch immediately to prevent potential host-level compromise by authenticated actors.

Description Summary:
The S3 protocol endpoint in LXC Incus is vulnerable to path traversal, allowing authenticated users to create arbitrary files on the host system.

Executive Summary:
A critical path traversal vulnerability in the LXC Incus S3 upload endpoint allows authenticated users to write arbitrary files to the host, facilitating potential command execution.

Vulnerability Details

CVE-ID: CVE-2026-48753

Affected Software: LXC Incus

Affected Versions: < 7.1.0

Vulnerability: This vulnerability is caused by improper validation of file paths during S3 protocol uploads (CWE-73). An authenticated attacker can exploit this to write files outside of the intended directory, which can be leveraged to execute arbitrary code on the host system.

Business Impact

Successful exploitation allows an attacker to gain persistent access to the host server by placing malicious files in sensitive locations. This compromises the integrity of the host and provides a pathway for further escalation or data theft. The CVSS score of 9.9 highlights the critical risk posed by this unauthorized write access.

Remediation Plan

Immediate Action: Update the LXC Incus software to version 7.1.0 or later to apply the necessary path validation fixes for the S3 upload endpoint.

Proactive Monitoring: Audit S3 upload logs for suspicious path characters or unexpected file creation events on the host.

Compensating Controls: If the S3 upload functionality is not required, disable the endpoint entirely to eliminate the attack surface until the patch can be applied.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 21, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly effective for attackers with access to the S3 upload interface.

Analyst Recommendation

Organizations utilizing the S3 upload feature in Incus must prioritize upgrading to version 7.1.0 immediately. The ease with which this path traversal can be exploited makes it a high-priority target for attackers seeking host-level persistence.

Description Summary:
A file system vulnerability in LXC Incus allows authenticated users to read or write arbitrary files on the host system using crafted instance backups or images.

Executive Summary:
A critical file path traversal vulnerability in LXC Incus permits authenticated users to perform arbitrary file operations on the host, leading to potential system-wide code execution.

Vulnerability Details

CVE-ID: CVE-2026-48752

Affected Software: LXC Incus

Affected Versions: < 7.2.0

Vulnerability: This flaw involves external control of file names or paths (CWE-73), allowing a specially crafted image or instance backup to escape intended boundaries. An authenticated attacker can leverage this to read sensitive host files or overwrite critical system files to achieve arbitrary command execution.

Business Impact

The ability to manipulate host files effectively grants the attacker control over the host operating system. This could result in the exfiltration of sensitive configuration files, the injection of malicious binaries, or complete host takeover. The CVSS score of 9.9 reflects the severity of this unauthorized file system access.

Remediation Plan

Immediate Action: Update the LXC Incus software to version 7.2.0 or later to ensure proper validation of image and backup file paths.

Proactive Monitoring: Monitor host file system integrity and review logs for unusual file access patterns or suspicious backup import activities.

Compensating Controls: Implement strict container image source controls and ensure that backups are only accepted from trusted, internal sources to prevent the introduction of malicious artifacts.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 21, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the level of control it provides over host file operations.

Analyst Recommendation

The severity of this issue necessitates an immediate patch deployment. Administrators should ensure all Incus instances are updated to version 7.2.0 to prevent potential host-level exploitation via malicious image or backup files.

Description Summary:
Incus instance snapshots improperly ignore security restrictions, allowing authenticated users to execute arbitrary commands on the host via lowlevel hooks.

Executive Summary:
A critical authorization bypass vulnerability in LXC Incus allows authenticated users to achieve full host system compromise through malicious instance snapshots.

Vulnerability Details

CVE-ID: CVE-2026-48751

Affected Software: LXC Incus

Affected Versions: < 7.2.0

Vulnerability: This vulnerability involves a missing authorization check (CWE-862) where instance snapshots fail to respect the restricted.containers.lowlevel=block configuration. An authenticated attacker can exploit this to trigger lowlevel hooks, such as raw.lxc or raw.qemu, leading to arbitrary command execution on the underlying host.

Business Impact

The potential for arbitrary command execution on the host server represents a total compromise of the virtualization environment. Successful exploitation allows an attacker to bypass container isolation, access sensitive host data, or move laterally within the infrastructure. With a CVSS score of 9.9, this vulnerability poses an extreme risk to confidentiality, integrity, and availability.

Remediation Plan

Immediate Action: Update the LXC Incus software to version 7.2.0 or later immediately to resolve the authorization flaw.

Proactive Monitoring: Audit Incus configuration logs for unexpected modifications to instance hooks or unauthorized attempts to utilize restricted lowlevel settings.

Compensating Controls: Restrict access to the Incus API and management interface to only trusted administrative accounts to minimize the attack surface for authenticated users.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 21, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly exploitable for any user with the ability to define container configurations.

Analyst Recommendation

Given the critical nature of this vulnerability and its potential for full host takeover, organizations must prioritize upgrading to version 7.2.0. Failure to patch leaves the host infrastructure vulnerable to any authenticated user capable of defining instance snapshots.

Description Summary:
A symlink-based vulnerability in the Incus /instances/$name/exec endpoint allows authenticated users to write arbitrary content to host files, potentially leading to arbitrary command execution.

Executive Summary:
A critical file-write vulnerability in the Incus container manager allows authenticated users to achieve host-level command execution by exploiting symlink handling in the exec output process.

Vulnerability Details

CVE-ID: CVE-2026-48750

Affected Software: LXC Incus

Affected Versions: < 7.2.0

Vulnerability: The vulnerability stems from improper validation of the exec-output directory, where a low-privileged authenticated user can redirect output files to arbitrary locations on the host system using symlinks (CWE-73).

Business Impact

By manipulating where command execution output is written, an attacker can overwrite critical system files or inject malicious scripts that the host system may execute. With a CVSS score of 9.9, this flaw poses an extreme risk to host availability and data confidentiality, as it facilitates a sandbox escape.

Remediation Plan

Immediate Action: Upgrade Incus to version 7.2.0 or later to implement the patch that secures symlink handling in the exec endpoint.

Proactive Monitoring: Review audit logs for unusual file creation events or unexpected symlink usage in the exec-output directories.

Compensating Controls: Limit access to the exec functionality within the container manager to only those users who strictly require it for operational tasks.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 21, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous as it allows for direct manipulation of the host filesystem from a container context.

Analyst Recommendation

The severity of this issue necessitates an immediate update to version 7.2.0. Organizations should verify that their container management policies prevent unauthorized access to the exec endpoint to minimize the attack surface until the update is deployed.

Description Summary:
Incus versions prior to 7.2.0 are vulnerable to arbitrary file read, write, or creation via crafted images, potentially leading to arbitrary command execution on the host system.

Executive Summary:
A critical vulnerability in the Incus system container manager allows authenticated users to achieve arbitrary command execution on the host via crafted images.

Vulnerability Details

CVE-ID: CVE-2026-48749

Affected Software: LXC Incus

Affected Versions: < 7.2.0

Vulnerability: This vulnerability involves improper external control of file paths (CWE-73), allowing a low-privileged authenticated user to manipulate host files through malicious container images.

Business Impact

Successful exploitation grants an attacker the ability to read sensitive host data or write files to the host filesystem, which can be leveraged to gain full control over the underlying server. Given the CVSS score of 9.9, this represents a critical risk to infrastructure integrity, potentially leading to total system compromise and data exfiltration.

Remediation Plan

Immediate Action: Update the Incus software to version 7.2.0 or later to apply the necessary security patch.

Proactive Monitoring: Monitor system logs for unauthorized file access attempts or suspicious container image deployments.

Compensating Controls: Restrict the ability to import or manage container images to trusted administrative personnel only.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 21, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly dangerous due to the potential for breakout from the container environment to the host.

Analyst Recommendation

This vulnerability presents a severe risk to containerized environments and requires immediate attention. Security teams should prioritize patching Incus to version 7.2.0 across all instances to prevent potential host-level exploitation.

Description Summary:
Incus versions prior to 6.23.0 are vulnerable to an arbitrary file write flaw where path traversal in systemd credential keys allows root-level writes to the host filesystem.

Executive Summary:
Incus virtual machine and container managers are vulnerable to a critical privilege escalation where an attacker can write arbitrary files as root on the host server, leading to full system compromise.

Vulnerability Details

CVE-ID: CVE-2026-33945

Affected Software: Incus

Affected Versions: Versions prior to 6.23.0

Vulnerability: The vulnerability exists in the handling of systemd.credential configuration keys. Because Incus allows periods in credential names, an attacker can use traversal sequences (e.g., ../../../root/.bashrc) to escape the intended directory and write files to the host filesystem with root privileges.

Business Impact

A successful exploit allows an attacker with instance configuration privileges to escalate to root on the host server. This can result in a total loss of host integrity, permanent denial of service, or the ability to compromise all other instances running on the same hardware. The CVSS score of 9.9 highlights the extreme severity of this host-escape scenario.

Remediation Plan

Immediate Action: Update Incus to version 6.23.0 or later to patch the configuration key parsing logic.

Proactive Monitoring: Audit instance configuration logs for any keys containing suspicious path traversal patterns or excessive use of periods in systemd.credential fields.

Compensating Controls: Limit the ability to modify instance configurations to highly trusted administrators and use mandatory access control (MAC) systems like AppArmor to restrict where the Incus daemon can write files.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Mar 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Host-escape vulnerabilities in virtualization platforms are among the most critical security risks. Administrators must apply the version 6.23.0 update immediately to prevent instance-to-host privilege escalation.

Description Summary:
The Incus web UI incorrectly validates authentication tokens, allowing unauthorized local or remote access to system containers and virtual machines.

Executive Summary:
A critical authentication bypass vulnerability in the Incus web interface allows unauthorized access to container and virtual machine management, potentially leading to full system compromise.

Vulnerability Details

CVE-ID: CVE-2026-33898

Affected Software: LXC Incus

Affected Versions: < 6.23.0

Vulnerability: The web server component of the Incus web interface suffers from improper authentication (CWE-287), where the system fails to correctly validate tokens provided via URL. This allows an attacker to bypass authentication controls and gain the same access level as the local user running the interface.

Business Impact

The vulnerability carries a CVSS score of 8.8, reflecting its high potential for severe impact. Successful exploitation grants an attacker unauthorized control over containerized environments and virtual machines, which may result in data exfiltration, system manipulation, or unauthorized resource consumption. Given that the web interface is used for management, the risk of total loss of confidentiality, integrity, and availability within the affected environment is significant.

Remediation Plan

Immediate Action: Update the Incus software to version 6.23.0 or later to apply the necessary authentication token validation patches.

Proactive Monitoring: Review system logs for unauthorized access attempts to the localhost ports used by the Incus web interface and monitor for unusual container or virtual machine lifecycle events.

Compensating Controls: Restrict access to the Incus web interface by binding the service to specific secure interfaces rather than all localhost addresses, and implement network segmentation to prevent remote access to the local web server port.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of March 28, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous because it allows an attacker to masquerade as an authenticated user, effectively bypassing all access control logic within the web management interface.

Analyst Recommendation

Organizations utilizing Incus for container or virtual machine management should prioritize this update immediately. While the vulnerability requires the web interface to be active and reachable, the potential for privilege escalation and unauthorized resource control necessitates a swift patching cycle to close the authentication gap introduced in earlier versions.

Description Summary:
Incus versions prior to 6.23.0 contain a critical sandbox escape in the pongo2 template implementation that allows arbitrary file reads and writes as root on the host server.

Executive Summary:
A critical vulnerability in Incus allows for arbitrary file read and write operations with root privileges on the host system by bypassing the template engine's filesystem isolation.

Vulnerability Details

CVE-ID: CVE-2026-33897

Affected Software: Incus

Affected Versions: Versions prior to 6.23.0

Vulnerability: The implementation of pongo2 templates within Incus fails to enforce chroot isolation. An attacker capable of creating or modifying instance templates can bypass the instance's filesystem boundaries to read or write any file on the host operating system with root authority.

Business Impact

This flaw permits an attacker to fully compromise the host server and all hosted instances. By reading sensitive host files (like /etc/shadow) or writing malicious binaries/scripts, an attacker can achieve persistent root access. The CVSS score of 9.9 reflects the critical nature of this host-level compromise.

Remediation Plan

Immediate Action: Upgrade Incus to version 6.23.0 immediately to restore proper template isolation and chroot enforcement.

Proactive Monitoring: Inspect all pongo2 template files for commands that attempt to access paths outside the standard instance directory structure.

Compensating Controls: Disable the use of instance templates if they are not strictly required for operations, or restrict template modification permissions to a minimal set of users.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Mar 26, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The failure of the chroot mechanism in the template engine is a high-priority security issue. Immediate patching is required to ensure that the isolation between the host and its containers remains intact.

Description Summary:
IncusOS configurations using systemd-cryptenroll allow attackers with physical access to bypass LUKS encryption and access data by substituting the root partition and leveraging TPM PCR policies.

Executive Summary:
A physical access vulnerability in IncusOS allows attackers to bypass LUKS disk encryption and access protected data, necessitating an immediate update to the hardened configuration.

Vulnerability Details

CVE-ID: CVE-2026-32606

Affected Software: LXC IncusOS

Affected Versions: < 202603142010

Vulnerability: This vulnerability is caused by an insufficiently protected credential configuration where the TPM releases the LUKS encryption key based on overly permissive PCR11 policies. An unauthenticated attacker with physical access can perform a filesystem substitution attack to intercept the key and gain unauthorized access to the system.

Business Impact

The ability to bypass disk encryption poses a severe risk to data confidentiality and integrity, as attackers can exfiltrate sensitive information or modify the operating system state. With a CVSS score of 7.6, this flaw represents a significant security risk for environments where physical security of the hardware cannot be guaranteed, potentially leading to total system compromise.

Remediation Plan

Immediate Action: Update to the patched version of IncusOS (202603142010 or later) which corrects the systemd-cryptenroll configuration.

Proactive Monitoring: Monitor physical access logs and implement tamper-evident hardware measures to identify unauthorized physical interactions with sensitive systems.

Compensating Controls: Ensure that full-disk encryption policies are strictly enforced and utilize hardware security modules that require additional user authentication beyond TPM-based unlocking where possible.

Exploitation Status

Public Exploit Available: Yes — a proof-of-concept repository exists on GitHub (github.com/gibmat/CVE-2026-32606-POC).

Analyst Notes: As of March 19, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The flaw is technically sophisticated but highly impactful for systems relying solely on default TPM-based disk unlocking.

Analyst Recommendation

The severity of this vulnerability is elevated by the presence of a public proof-of-concept and the potential for complete data exposure. Administrators must prioritize updating IncusOS to the specified fixed version to restrict the TPM's ability to release encryption keys to unauthorized boot environments. Failure to address this flaw leaves protected data vulnerable to physical bypass attacks.

Description Summary:
Incus versions 6.21.0 and below are vulnerable to directory traversal and symbolic link attacks during container image templating, allowing host-level arbitrary file read, write, and command execution.

Executive Summary:
A critical vulnerability in the Incus system container manager allows authenticated users to achieve arbitrary command execution on the host system.

Vulnerability Details

CVE-ID: CVE-2026-23954

Affected Software: LXC Incus

Affected Versions: >= 6.1.0, <= 6.20.0, <= 6.0.5

Vulnerability: This flaw involves improper path validation during the processing of image templates. An authenticated user with permissions to launch containers can manipulate source and target paths to escape the container environment, resulting in host-level file system compromise and code execution.

Business Impact

The ability for a container-level user to escape to the host system represents a total compromise of the virtualization layer. This vulnerability poses a severe risk of unauthorized data access, lateral movement across the infrastructure, and full loss of control over the host server. Given the CVSS score of 8.7, this is considered a high-severity issue that requires immediate attention to prevent system-wide exploitation.

Remediation Plan

Immediate Action: As no fixed version is currently available, administrators should restrict the ability to launch containers using custom images to highly trusted users. Monitor the official LXC Incus security advisory for the release of versions 6.0.6 and 6.21.0.

Proactive Monitoring: Review audit logs for suspicious container configuration patterns, specifically those involving custom image metadata. Monitor for unauthorized file access or unexpected process creation on the host server originating from container-related services.

Compensating Controls: Implement strict host-level access controls and ensure that container runtimes are isolated with proper kernel security modules like AppArmor or SELinux. Reduce the attack surface by limiting the privileges of the incus group members.

Exploitation Status

Public Exploit Available: Yes, a published proof-of-concept exists, attributed to the technical documentation and files provided in the vulnerability references.

Analyst Notes: As of January 26, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly exploitable for any user with the ability to define custom container images.

Analyst Recommendation

This vulnerability presents a significant risk to containerized environments due to the potential for full host system takeover. Security teams must treat this as a priority and implement the suggested access restrictions immediately. Once the vendor releases the patched versions 6.0.6 or 6.21.0, administrators should verify the integrity of their container images and apply the updates across all affected nodes without delay.

Description Summary:
A CRLF injection vulnerability in Incus allows authenticated users to execute arbitrary commands on the host system via manipulated container configurations.

Executive Summary:
A high-severity CRLF injection vulnerability in Incus allows an authenticated user to achieve arbitrary command execution on the host, necessitating an immediate update to version 6.21.0 or 6.0.6.

Vulnerability Details

CVE-ID: CVE-2026-23953

Affected Software: LXC Incus

Affected Versions: >= 6.1.0, <= 6.20.0, <= 6.0.5

Vulnerability: The software fails to properly neutralize CRLF sequences in environment variables used within custom YAML container configurations. This flaw allows an authenticated user, such as a member of the incus group, to perform newline injection and insert unauthorized lifecycle hooks, leading to command execution on the host.

Business Impact

This vulnerability carries a CVSS score of 8.7, reflecting a high risk of total system compromise. Successful exploitation grants an attacker the ability to escape container restrictions and execute arbitrary commands on the host operating system, which could lead to complete data exfiltration, unauthorized access to sensitive infrastructure, and severe service disruption.

Remediation Plan

Immediate Action: Update Incus to version 6.21.0 or 6.0.6 as soon as these versions are available from the vendor.

Proactive Monitoring: Review system logs and container configuration files for anomalous environment variable definitions or unexpected lifecycle hook entries.

Compensating Controls: Restrict membership of the incus group to only highly trusted administrative users to minimize the attack surface until patches can be applied.

Exploitation Status

Public Exploit Available: Yes — a published proof-of-concept exists, attributed to the security researcher's technical write-up and files referenced in the official GitHub advisory.

Analyst Notes: As of January 26, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is inherently dangerous due to its ability to bypass container isolation via simple configuration injection.

Analyst Recommendation

Given the potential for full host system compromise, this vulnerability should be treated with high urgency. Administrators must monitor the official Incus repository for the release of versions 6.21.0 and 6.0.6, and apply these updates immediately upon availability. Until the patch is applied, limit administrative access to the container manager to prevent exploitation by unauthorized or malicious users.