CVE-2026-63343: Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root
Incus is a system container and virtual machine manager. Prior to version 7.3.0, a malicious image containing a `metadata.yaml` symlink pointing to an arbitrary host path allows an authenticated Incus user to read or overwrite any file on the host as root via the instance metadata API. The `exec-output` and `templates/` paths were patched in a prior release using `Lstat` rejection and `os.OpenRoot` confinement; `metadata.yaml` was not included in either patch and remains exploitable. Version 7.3.0 patches the issue.
Security readout for executives and security teams
Plain-English summary
An authenticated Incus user can use a specially prepared image to make the instance metadata API read or overwrite arbitrary host files with root privileges. This could expose secrets, compromise the host, disrupt workloads, and potentially affect other tenants. Incus versions before 7.3.0 are affected.
Executive priority
Treat this as an immediate patching priority for affected multi-user or multi-tenant Incus systems. Root-level host file access can turn limited platform access into full host compromise. Accelerate version verification and access review, while avoiding claims of an ongoing campaign because active exploitation is not established.
Technical view
A malicious image can replace metadata.yaml with a symbolic link to an arbitrary host path. Incus then follows that link during metadata API operations, enabling root-level host file reads or writes. Earlier confinement and symbolic-link protections covered exec-output and templates/ but omitted metadata.yaml. Version 7.3.0 corrects the omission.
Likely exposure
Exposure requires Incus earlier than 7.3.0 and an authenticated user able to introduce or use a malicious image and access the instance metadata API. Shared or multi-tenant environments with less-trusted Incus users have the greatest risk. The supplied sources do not identify specific default configurations or internet-exposure requirements.
Exploitation context
The CVSS 3.1 score is 9.9, reflecting low-complexity, network-reachable exploitation by a low-privileged authenticated user without user interaction. Successful abuse crosses a security boundary and can affect confidentiality, integrity, and availability. The supplied bundle says this CVE is not in KEV and provides no evidence of active exploitation.
Researcher notes
The flaw is classified as CWE-73 and concerns insufficient confinement of a filename or path. The important regression detail is that prior protections using Lstat rejection and os.OpenRoot covered related paths but excluded metadata.yaml. The supplied evidence does not describe public proof-of-concept availability, observed attacks, or indicators of compromise.
Mitigation direction
Upgrade Incus to version 7.3.0 or later.
Prioritize shared environments containing untrusted or delegated Incus users.
Restrict image-management and instance-metadata access until upgrades are complete.
Check the vendor advisory for any additional operational guidance.
Validation and detection
Inventory Incus hosts and confirm every installed version is 7.3.0 or later.
Identify users permitted to import images or access instance metadata.
Review relevant activity for unexpected metadata operations involving metadata.yaml.
Check sensitive host files for unexplained reads, modifications, or integrity changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-73 · source CWE mapping
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.