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

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.

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.

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.

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

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.