Security readout for executives and security teams
Plain-English summary
A malicious Incus image server can abuse vulnerable Incus clients to write files outside their intended location. That may ultimately allow commands to run as root on the Incus server, creating a risk of complete system compromise. Incus versions before 7.2.0 are affected; version 7.2.0 fixes the issue.
Executive priority
Treat remediation as urgent for affected Incus environments, especially those using external or insufficiently trusted image servers. The potential outcome is root-level compromise, while the published fix is a direct upgrade to 7.2.0. Do not claim an incident solely from version exposure; investigate affected systems based on their image-server relationships and activity.
Technical view
Before 7.2.0, Incus insufficiently validates a crafted Incus-Image-Hash response header from a malicious image server. This permits arbitrary file writes through the client and can lead to root command execution on the server. The published CVSS 3.1 score is 9.9, with network access, low complexity, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure exists where Incus versions earlier than 7.2.0 communicate with a malicious or compromised image server. The supplied evidence does not establish how commonly vulnerable deployments use attacker-controlled image sources, so organization-specific exposure requires inventory and configuration review.
Exploitation context
The supplied record does not identify active exploitation, and this CVE is not listed as KEV in the bundle. Exploitation requires a malicious image server to return a crafted header. The low-complexity, no-user-interaction rating increases concern, but no exploit prevalence or public weaponization evidence is provided.
Researcher notes
The vulnerability is categorized as CWE-20 and centers on trust and validation of Incus-Image-Hash. The source bundle confirms arbitrary file write and possible root command execution but provides no detailed affected branch matrix, indicators of compromise, exploitation telemetry, or verified workaround beyond upgrading. Avoid extrapolating impact to products other than lxc Incus.
Mitigation direction
- Upgrade affected Incus installations to version 7.2.0 or later.
- Prioritize systems that can communicate with untrusted or externally controlled image servers.
- Until upgraded, avoid untrusted image servers as temporary risk reduction, not a substitute for patching.
- Consult the vendor advisory for any additional deployment-specific guidance.
Validation and detection
- Inventory Incus installations and identify every version earlier than 7.2.0.
- Verify upgraded systems report Incus version 7.2.0 or later.
- Review configured image servers and identify untrusted, external, or unexpectedly changed sources.
- Investigate vulnerable systems for unexpected file modifications or root command execution associated with image operations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-48769 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/lxc/incus/security/advisories/GHSA-f6m5-xw2g-xc4xCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.