github.com/lxc/incus/v7/cmd/incusd

CVE-2026-48769

CVE-2026-48769 is a critical-severity improper input validation vulnerability in github.com/lxc/incus/v7/cmd/incusd (go), affecting versions < 7.2.0. It is fixed in 7.2.0.

Key facts
CVSS score
9.9
Critical
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
github.com/lxc/incus/v7/cmd/incusd
Fixed in
7.2.0
Disclosed
2026

Summary

Summary An arbitrary file write exists in the Incus client when a malicious image server returns a crafted Incus-Image-Hash header. This can lead to arbitrary command execution as root on the server. Details cmd/incusd/images.go:611-684 handles source.type=url by HEADing the user-supplied URL, reading Incus-Image-Hash and Incus-Image-URL, and passing them to imageDownload() as Alias and Server. cmd/incusd/daemonimages.go:91-92 defaults fp to the caller-controlled alias string. cmd/incusd/daemonimages.go:333-335 builds destName := filepath.Join(destDir, fp). cmd/incusd/daemonimages.go:469-523 enters the direct protocol branch, opens destName with os.Create(), and copies the HTTP response into that file. cmd/incusd/daemonimages.go:528-532 validates the SHA-256 only after the file has already been created and populated. cmd/incusd/daemon_images.go:337-344 cleanup only runs after the copy returns; a slow or held response extends the arbitrary-write window. A malicious image server returning something along the following will cause the arbitrary file write. PoC The script below creates a malicious image server and requests an Incus server to fetch the image. File write occurs when the image is unpacked. The following script was generated by an LLM. Impact An arbitrary file write on the client with root privileges; possibly leading to arbitrary command execution.

Impact

What is improper input validation?

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Severity and exposure

CVE-2026-48769 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.

Affected versions

go

  • github.com/lxc/incus/v7/cmd/incusd (< 7.2.0)

Security releases

  • github.com/lxc/incus/v7/cmd/incusd → 7.2.0 (go)
Kodem intelligence

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-48769 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-48769 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-48769 in your environment

Remediation advice

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.

Frequently asked questions about CVE-2026-48769

What is CVE-2026-48769?

CVE-2026-48769 is a critical-severity improper input validation vulnerability in github.com/lxc/incus/v7/cmd/incusd (go), affecting versions < 7.2.0. It is fixed in 7.2.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2026-48769?

CVE-2026-48769 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.

Which versions of github.com/lxc/incus/v7/cmd/incusd are affected by CVE-2026-48769?

github.com/lxc/incus/v7/cmd/incusd (go) versions < 7.2.0 is affected.

Is there a fix for CVE-2026-48769?

Yes. CVE-2026-48769 is fixed in 7.2.0. Upgrade to this version or later.

Is CVE-2026-48769 exploitable, and should I be worried?

Whether CVE-2026-48769 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

What actually determines whether CVE-2026-48769 is exploitable, and how bad it is?

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.

How do I fix CVE-2026-48769?

Upgrade github.com/lxc/incus/v7/cmd/incusd to 7.2.0 or later.

Stop the waste.
Protect your environment with Kodem.