Skip to content
Fencer Vulns
critical 9.9

CVE-2026-48769 json

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

published 2026-06-26 4 mo ago modified 2026-11-06 2 d ago also GHSA-f6m5-xw2g-xc4x , GO-2026-5806 , EUVD-2026-63983

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Incus is a system container and virtual machine manager. Prior to version 7.2.0, 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. Version 7.2.0 patches the issue.

Patch / fix

  • go github.com/lxc/incus/v7/cmd/incusd 7.2.0
  • go github.com/lxc/incus/v7 7.2.0
  • lxd Debian 13 5.0.2+git20231211.1364ae4-9+deb13u7
  • incus Debian 13 6.0.4-2+deb13u8
  • incus Debian 14 7.0.0-5

debian advisories DEBIAN-CVE-2026-48769

  • incus openSUSE Tumbleweed 7.4-1.1
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:11651-1openSUSE-SU-2026:21483-1

  • incus Alpine 3.24 7.0.1-r0

alpine advisories ALPINE-CVE-2026-48769

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-48769 updated cvss 9.9

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

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2 mo ago

Exploit prediction

0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/lxc/incus/security/advisories/GHSA-f6m5-xw2g-xc4x referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/lxc/incus/v7/cmd/incusd
<7.2.0
7.2.0
go github.com/lxc/incus
all versions
 no fix listed
go github.com/lxc/incus/v6
all versions
 no fix listed
go github.com/lxc/incus/v7
<7.2.0
7.2.0

Affected products

  • lxc incus
  • canonical lxd

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.