Critical Incus Vulnerability (CVE-2026-48752) Allows Host Arbitrary File Read/Write Leading to RCE
A critical vulnerability, CVE-2026-48752, in Incus versions prior to 7.2.0 allows an unauthenticated attacker to achieve arbitrary file read and write on the host system via specially crafted container images or instance backups containing unsanitized symlinks, potentially leading to arbitrary command execution as root.
A critical vulnerability tracked as CVE-2026-48752 has been identified in Incus, a Linux container manager, affecting versions prior to 7.2.0. This flaw allows a malicious actor to perform arbitrary file read and write operations on the underlying host system. The exploitation vector involves crafting a malicious container image or instance backup that includes a top-level templates symlink. When Incus unpacks such an artifact, it fails to properly sanitize this symlink, enabling the attacker to redirect operations intended for the templates directory to any arbitrary path on the host, such as /etc/cron.d. This capability can be leveraged to inject malicious cron jobs or modify other sensitive system files, ultimately leading to arbitrary command execution with root privileges on the host. This vulnerability poses a significant risk to the integrity and security of systems running vulnerable Incus instances.
Attack Chain
- The attacker crafts a malicious Incus container image or instance backup (
.tararchive). - Within this archive, a top-level symlink named
templatesis created, pointing to a sensitive host directory (e.g.,/etc/cron.d). - The attacker distributes this malicious image or backup, which is then imported or restored on a vulnerable Incus host using
incus image importorincus import. - During the unpacking process, Incus's
archive.Unpack(for images) orrsync.LocalCopy(for backups) follows thetemplatessymlink due to insufficient sanitization. - The attacker then uses
incus config template createorincus config template editcommands, targeting the newly imported malicious instance/image. - Due to the symlink, these
incuscommands inadvertently write arbitrary content to the sensitive host directory (e.g., creating a new cron job file in/etc/cron.d). - The malicious cron job is executed by the host's cron daemon, achieving arbitrary command execution, often as root, on the host system.
- The attacker gains full control over the Incus host, enabling further malicious activities like data exfiltration or deploying additional malware.
Impact
The successful exploitation of CVE-2026-48752 leads to arbitrary file read and write capabilities on the Incus host system. This direct access to the host filesystem allows attackers to modify critical system files, inject malicious configurations (such as cron jobs), and ultimately achieve arbitrary command execution, often with root privileges. The consequences include complete system compromise, unauthorized data access, persistence mechanisms, and potential disruption of services. While no specific victim count or sectors are mentioned, any organization utilizing vulnerable Incus installations could be at risk of severe security breaches and operational disruption.
Recommendation
- Patch Incus immediately to version 7.2.0 or newer to address CVE-2026-48752 as advised by the vendor.
- Deploy the Sigma rule below to detect suspicious
incusdwrite operations to sensitive system directories. - Enable comprehensive
file_eventlogging for Linux systems to capture modifications within critical directories like/etc/cron.d/,/etc/,/bin/,/sbin/by theincusdprocess.
Detection coverage 1
Detects CVE-2026-48752 Exploitation - Incus Writing to Sensitive System Directories
highDetects CVE-2026-48752 exploitation where the 'incusd' process writes or creates files in sensitive system directories (e.g., /etc/cron.d) due to a symlink following vulnerability. This indicates arbitrary file write on the host.
Detection queries are available on the platform. Get full rules →