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

CVE-2026-48755

CVE-2026-48755 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 Improper validation of user-provided backup compression algorithm leads to argument injection in the constructed command line. This leads to an arbitrary file write on the host, possibly leading to arbitrary command execution. Details Incus validates compression_algorithm by parsing it into fields and checking only the first token against an allowlist: Extra arguments are not rejected. compressFile() then prepends -c and passes the remaining user-supplied fields to the compressor: With a value like: the daemon executes the equivalent of: PoC The following was generated by an LLM model. Impact Improperly validated compression algorithm argument leads to argument injection leading to arbitrary file write with zstd and possibly 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-48755 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-48755 is reachable in your applications. Explore open-source security for your team.

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

Already deployed Kodem? See CVE-2026-48755 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-48755

What is CVE-2026-48755?

CVE-2026-48755 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-48755?

CVE-2026-48755 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-48755?

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

Is there a fix for CVE-2026-48755?

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

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

Whether CVE-2026-48755 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-48755 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-48755?

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

Stop the waste.
Protect your environment with Kodem.