LXD has arbitrary file write on client due to trusted image hash — GHSA-PJFF-C2WC-F6JM
GitHub · GitHub · GHSA-PJFF-C2WC-F6JM
ID
GHSA-PJFF-C2WC-F6JM
GHSA-PJFF-C2WC-F6JM
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-f6m5-xw2g-xc4x ### Summary An arbitrary file write exists in the Incus client when a malicious image server returns a crafted `Incus-Image-Hash` header. This can lead to arbitrary command execution as root on the server. ### Details - `cmd/incusd/images.go:611-684` handles `source.type=url` by HEADing the user-supplied URL, reading…
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-PJFF-C2WC-F6JM
- 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.