CVE-2026-48749 is a critical-severity security vulnerability in github.com/lxc/incus/v7/cmd/incusd (go), affecting versions < 7.2.0. It is fixed in 7.2.0.
Summary A specially crafted image can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution. Details Incus validates an image as soon as it sees a normal metadata.yaml and a rootfs/ entry, but full extraction can later process a duplicate top-level rootfs symlink. Later, the stopped-container file API opens d.RootfsPath() and passes that file descriptor to forkfile, which chroots to it. In practice, this allows a malicious actor to access the host's filesystem with root privileges. PoC Below, we map the container's rootfs to / on the host, but it can be mapped anywhere. We then retrieve the host's /etc/shadow file and create a file in /. Impact Arbitrary file read and write on the host via unsanitized symlink; possibly leading to command execution.
CVE-2026-48749 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (7.2.0). Upgrading removes the vulnerable code path.
go
github.com/lxc/incus/v7/cmd/incusd (< 7.2.0)github.com/lxc/incus/v7/cmd/incusd → 7.2.0 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-48749 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-48749 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-48749 in your environment →Upgrade github.com/lxc/incus/v7/cmd/incusd to 7.2.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-48749 is a critical-severity security vulnerability in github.com/lxc/incus/v7/cmd/incusd (go), affecting versions < 7.2.0. It is fixed in 7.2.0.
CVE-2026-48749 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/lxc/incus/v7/cmd/incusd (go) versions < 7.2.0 is affected.
Yes. CVE-2026-48749 is fixed in 7.2.0. Upgrade to this version or later.
Whether CVE-2026-48749 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/lxc/incus/v7/cmd/incusd to 7.2.0 or later.