Host command execution via exec-output symlink
Published Aug 21, 2026 · Updated Aug 21, 2026
Arbitrary file write in Incus before 7.2.0 allows remote authenticated users to execute commands on the host through a crafted image. During image unpacking, a top-level exec-output symlink is preserved; instance_exec.go accepts the existing path, and os.OpenFile follows it when record-output stores command output. Access to instance image import and execution is required, after which controlled stdout can be placed in a host directory such as the system cron directory.
Summary
What happened
Arbitrary file write in Incus before 7.2.0 allows remote authenticated users to execute commands on the host through a crafted image. During image unpacking, a top-level exec-output symlink is preserved; instance_exec.go accepts the existing path, and os.OpenFile follows it when record-output stores command output. Access to instance image import and execution is required, after which controlled stdout can be placed in a host directory such as the system cron directory.
The record
- CVE
- CVE-2026-48750
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- Linux Containers
- Product
- Incus
- Classifications
- CWE-73, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream exec-output symlink proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo