CVE-2026-48750: Incus has an arbitrary file write on host via `exec-output` symlink in crafted image
Incus is a system container and virtual machine manager. Prior to version 7.2.0, the `record-output` parameter of the `/instances/$name/exec` endpoint stores the output of the command in the `exec-output` directory of the instance. If `exec-output` is a symlink, file named `exec_UUID.stdout` and `exec_UUID.stderr` can be written to an arbitrary location where the `.stdout` file will contain arbitrary content. This behavior can be abused for arbitrary command execution. Version 7.2.0 contains a patch.
Security readout for executives and security teams
Plain-English summary
A user with limited privileges could abuse a crafted Incus image to write attacker-controlled content onto the host and potentially execute commands. Successful exploitation could compromise the host and workloads it manages. Incus versions earlier than 7.2.0 are affected.
Executive priority
Treat this as an immediate patching priority for internet-accessible, shared, or untrusted-tenant Incus environments. The vulnerability crosses the container boundary and may expose the host and other workloads. Restrict exec API access while upgrades and compromise checks are completed.
Technical view
The exec endpoint’s `record-output` feature writes stdout and stderr beneath an instance’s `exec-output` directory. Before 7.2.0, a crafted image could make that directory a symlink, redirecting `exec_UUID.stdout` and `exec_UUID.stderr` to host locations. Attacker-controlled stdout enables arbitrary file content and may lead to command execution. This is classified as CWE-73.
Likely exposure
Exposure exists on Incus deployments earlier than 7.2.0 where an attacker can invoke the instance exec endpoint and supply or control the crafted instance image conditions. The CVSS vector indicates network access, low privileges, no user interaction, and impact crossing the instance-to-host security boundary.
Exploitation context
The supplied sources do not establish active exploitation, inclusion in CISA KEV, or availability of a public exploit. However, the published advisory describes a low-complexity path from limited privileges to host-level file write and possible command execution, making vulnerable deployments urgent to remediate.
Researcher notes
The decisive condition is symlink handling for an instance-controlled `exec-output` directory during recorded exec operations. The `.stdout` output can contain attacker-controlled content, supporting arbitrary host file writes and potential command execution. The bundle does not provide affected configuration nuances, indicators of compromise, or evidence of exploitation beyond the vendor-described behavior.
Mitigation direction
Upgrade every affected Incus deployment to version 7.2.0 or later.
Until upgraded, restrict the instance exec API to trusted administrators.
Review the vendor advisory for deployment-specific precautions or backport guidance.
Investigate affected hosts for unexpected `exec-output` symlinks, files, or host-level changes.
Validation and detection
Inventory Incus versions and identify every deployment running a release earlier than 7.2.0.
Confirm remediated hosts report Incus version 7.2.0 or later.
Review retained API and instance logs for unusual `record-output` activity.
Perform host integrity checks around unexpected files or configuration changes associated with affected instances.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.
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.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-73 · source CWE mapping
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.