Is CVE-2026-48752 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-48752 being exploited in the wild.

How severe is CVE-2026-48752?

Critical severity, with a CVSS score of 9.9, published 21 August 2026.

Which products and versions are affected?

github.com/lxc/incus (Go) SEMVER:introduced=0; github.com/lxc/incus/v6 (Go) SEMVER:introduced=0; github.com/lxc/incus/v7 (Go) SEMVER:introduced=0,fixed=7.2.0; github.com/lxc/incus/v7/cmd/incusd (Go) < 7.2.0, SEMVER:introduced=0,fixed=7.2.0.

Is there a fix for CVE-2026-48752?

Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.2.0 or later; github.com/lxc/incus/v7/cmd/incusd (Go): upgrade to 7.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48752 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-48752?

Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48752: Incus arbitrary file read and write via templates symlink

Q: Is there a fix for CVE-2026-48752?

Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.2.0 or later; github.com/lxc/incus/v7/cmd/incusd (Go): upgrade to 7.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-48752 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-48752?

Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48752 · Severity: critical · CVSS 9.9 · Published 2026-08-21

Incus, a container and virtual machine management tool, is vulnerable to a flaw where a specially crafted container image or backup can be used to read or write any file on the host server. An attacker with the ability to import images or backups could use this to modify critical system files, potentially leading to full control over the host machine and its operations. This poses a significant risk to data confidentiality and system availability.

Technologies: github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go), github.com/lxc/incus/v7/cmd/incusd (Go). Vendors: Go.

Quick answers

Is CVE-2026-48752 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48752 being exploited in the wild.
How severe is CVE-2026-48752?: Critical severity, with a CVSS score of 9.9, published 21 August 2026.
Which products and versions are affected?: github.com/lxc/incus (Go) SEMVER:introduced=0; github.com/lxc/incus/v6 (Go) SEMVER:introduced=0; github.com/lxc/incus/v7 (Go) SEMVER:introduced=0,fixed=7.2.0; github.com/lxc/incus/v7/cmd/incusd (Go) < 7.2.0, SEMVER:introduced=0,fixed=7.2.0.
Is there a fix for CVE-2026-48752?: Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.2.0 or later; github.com/lxc/incus/v7/cmd/incusd (Go): upgrade to 7.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48752 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-48752?: Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/lxc/incus/v7 (Go): upgrade to 7.2.0 or later
```
go get github.com/lxc/incus/v7@v7.2.0
```
github.com/lxc/incus/v7/cmd/incusd (Go): upgrade to 7.2.0 or later
```
go get github.com/lxc/incus/v7/cmd/incusd@v7.2.0
```

Technical details

A path traversal vulnerability exists in Incus due to improper sanitization of symlinks within container images and instance backups. For container images, the 'archive.Unpack' function fails to reject top-level 'templates' symlinks during extraction. For instance backups, the 'rsync.LocalCopy' operation uses archive mode without the '--safe-links' flag, allowing a 'templates' symlink to point to arbitrary locations on the host filesystem. An attacker with low privileges can exploit this by importing a malicious image or backup, then using the template management commands to read from or write to host files (e.g., /etc/cron.d). This can lead to arbitrary command execution with root privileges on the host. The issue is fixed in version 7.2.0.

Affected products

Linux Containers (LXC) Incus < 7.2.0

Identifiers

CVE-2026-48752
GHSA-vxp5-584q-c479
GO-2026-5803

Timeline

2026-06-25: disclosed
2026-06-26: advisory
2026-06-26: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.