Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-63293: A link following vulnerability in LXD allows an attacker to achieve arbitrary file read and write operations o

52
This month
CRITICAL 9.9UPGRADE

CVE-2026-63293 is a critical-severity flaw (CVSS 9.9) affecting lxd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A link following vulnerability in LXD allows an attacker to achieve arbitrary file read and write operations on the host system. When importing or unpacking an image archive, LXD fails to validate whether the metadata.yaml file is a symbolic link. An attacker can exploit this flaw by providing a crafted image archive with a symlinked metadata.yaml file pointing to target file paths on the host system.

Why this priority

  • Critical severity
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score9.9 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.6% (top 52%)
CISA exploited listNo
WeaknessCWE-59
Published2026-08-12
Last modified2026-10-24
Publisher (CNA): Canonical Ltd. · Vendor: canonical

Share: LinkedIn · X · Reddit

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

canonical lxd UPGRADE
Affected: >= 4.0.0 and < 4.0.12
Fixed in: 4.0.12
Safe to downgrade to: a release before 4.0.0
1. Check installed version
apt-cache policy lxd || rpm -q lxd || lxd --version
2. UPGRADE to 4.0.12 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade lxd
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade lxd
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)
apt-cache madison lxd sudo apt install lxd=<VERSION_BEFORE_4.0.0> sudo apt-mark hold lxd
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list lxd sudo dnf downgrade lxd-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add lxd
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Fedora 46 · rubygem-eventmachine · FIXED · 1.2.7-37.fc46 · FEDORA-2026-7194c202a2 · source
sudo dnf upgrade --advisory=FEDORA-2026-7194c202a2
Debian 12 · lxd · NO FIX YET
Debian 13 · lxd · NO FIX YET

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-63293?

lxd: upgrade to 4.0.12. Exact commands for each OS are on this page.

Is CVE-2026-63293 being exploited?

CVE-2026-63293 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-63293 affect?

CVE-2026-63293 affects lxd. Severity is critical (CVSS 9.9). A link following vulnerability in LXD allows an attacker to achieve arbitrary file read and write operations on the host system. When importing or unpacking an image archive, LXD fails to validate whether the metadata.yaml file is a symboli

How urgent is CVE-2026-63293?

Priority 52/100. Critical severity; Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.