CVE-2026-63293: Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root

Published Aug 12, 2026
·
Updated

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.

Affected Software

1 affected component
Canonical LXD

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.0.12
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.0.8
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.12.6
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.10

Event History

Aug 12, 2026
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
RemedyDescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-63293?

CVE-2026-63293 has a critical severity rating of 9.9.

2

How do I fix CVE-2026-63293?

To fix CVE-2026-63293, update Canonical LXD to the latest patched version eliminating the symbolic link vulnerability.

3

What impact does CVE-2026-63293 have on my system?

CVE-2026-63293 allows arbitrary file read and write operations on the host filesystem, potentially giving attackers root access.

4

Who is affected by CVE-2026-63293?

Users of Canonical LXD who utilize image archives are affected by CVE-2026-63293 due to the lack of validation for symbolic links.

5

When was CVE-2026-63293 published?

CVE-2026-63293 was published on August 12, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203