Incus has an arbitrary file write on its client due to trusted image hash

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-48769: 0.73% estimated exploitation activity in the next 30 days; percentile 54.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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/daemonimages.go:337-344 cleanup only runs after the copy returns; a slow or held response extends the arbitrary-write window. A malicious image…

Published by the source

26 Jun 2026, 19:13 UTC

Last modified by the source

26 Jun 2026, 19:13 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f6m5-xw2g-xc4x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48769

Advisory: Incus has an arbitrary file write on its client due to trusted image hash
IDs: CVE-2026-48769, GHSA-f6m5-xw2g-xc4x
Record: https://patchnext.com/advisories/cve-2026-48769 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lxc/incus/v7/cmd/incusd 7.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lxc/incus/v7/cmd/incusd: affected < 7.2.0; fixed in 7.2.0

## Suggested inspection (read-only)
- Go github.com/lxc/incus/v7/cmd/incusd: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lxc/incus/v7/cmd/incusd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f6m5-xw2g-xc4x (GitHub-reviewed advisory GHSA-f6m5-xw2g-xc4x lists affected ranges: Go github.com/lxc/incus/v7/cmd/incusd >=0 <7.2.0)

Commands are suggestions: review each one before running it.