LXD has arbitrary file write on host via `exec-output` symlink in crafted image — GHSA-9J25-MM2H-2F76
GitHub · GitHub · GHSA-9J25-MM2H-2F76
ID
GHSA-9J25-MM2H-2F76
GHSA-9J25-MM2H-2F76
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
critical
critical
CVSS
9.9
9.9
Summary
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…
Timeline
- Published by source
- 2026-11-06
Risk context
- Reported severity or threat level: critical.
- Reported CVSS score: 9.9 out of 10.
- Review exposure for the affected product or family: go: github.com/canonical/lxd.
Product
go: github.com/canonical/lxd
What to do
General, cautious steps (verify details in the official source):
- Prioritize patching or mitigation immediately (treat as actively risky).
- Identify affected product versions in your inventory and verify whether you are impacted.
- Apply vendor patches/updates or recommended mitigations as soon as available.
- Read the official advisory for exact affected versions and remediation steps.
Official advisory
Evidence and provenance
- Canonical advisory ID
- GHSA-9J25-MM2H-2F76
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-11-06
- Last source activity
- 2026-11-06
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.