Is CVE-2026-48750 exploited in the wild?

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

How severe is CVE-2026-48750?

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-48750?

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-48750 attacked?

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

Am I affected by CVE-2026-48750?

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-48750: LXC Incus arbitrary file write via exec-output symlink

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

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-48750 attacked?

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

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

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-48750 · Severity: critical · CVSS 9.9 · Published 2026-08-21

Incus is a container and virtual machine management tool. A vulnerability allows an attacker to use a specially crafted container image to write files to the host operating system's filesystem. This could allow an attacker to gain full control over the host server, potentially leading to data theft or service disruption.

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-48750 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48750 being exploited in the wild.
How severe is CVE-2026-48750?: 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-48750?: 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-48750 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-48750?: 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 vulnerability in Incus (specifically the incusd component) exists where the 'record-output' parameter of the /instances/$name/exec endpoint fails to properly validate the 'exec-output' directory. If a crafted image contains a top-level symlink named 'exec-output' pointing to a host directory (e.g., /etc/cron.d), the 'os.OpenFile' function follows this symlink when recording command output. An attacker with low privileges can trigger this by launching an instance from a malicious image and executing a command with output recording enabled. This results in the creation of .stdout and .stderr files on the host, which can be leveraged for arbitrary command execution on the host system. The issue is fixed in version 7.2.0.

Affected products

LXC Incus < 7.2.0

Identifiers

CVE-2026-48750
GHSA-73hr-m85f-64v9
GO-2026-5801

Timeline

2026-06-25: disclosed
2026-06-26: advisory: GHSA-73hr-m85f-64v9 published
7.2.0: patched

References

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