Servers and applications
CVE-2026-63125
Arbitrary file write on host via backup.yaml symlink in crafted image
- Severity
- Critical 9.9
- Published
- 30 Jul 2026
- Last changed
- 30 Jul 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 7.3.0
- Exploit chance
- 0.7% in the next 30 daysHigher than 52% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Link following (CWE-59)CWE-61
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H- Also known as
- GHSA-6rqx-22hc-qm36
- Sources
- Project advisories (GitHub)
Description
An unprivileged, project-confined Incus user (a non-admin TLS/RBAC identity with can_create_images and can_create_instances) can execute arbitrary code as root on the host. A crafted image ships backup.yaml as a symlink to a host file. When the root daemon writes the instance's backup file, it follows the symlink. Confirmed on the latest release, v7.2.0.
When an image is unpacked, only a rootfs symlink is rejected. All other members of the attacker's metadata tarball are extracted verbatim into the instance directory, and the subsequent backup-file write follows symlinks.
- internal/server/storage/utils.go:608. archive.Unpack(imageFile, destPath, …) unpacks the metadata tarball into destPath == inst.Path(). The guard at utils.go:611 only os.Lstats rootfs, so a planted backup.yaml symlink survives.
- internal/server/storage/backend.go:6966-6967. UpdateInstanceBackupFile() does os.Create(filepath.Join(inst.Path(), "backup.yaml")) with no O_NOFOLLOW and no Lstat.
Affected software
| Software | Affected versions |
|---|---|
IncusServers and applications · github:lxc/incus |
|
About Incus
container manager for system containers
- GitHub stars
- 6,644GitHub, 15 Nov 2026
- Forks
- 522GitHub, 15 Nov 2026
- Latest release
- v7.6.0GitHub, 15 Nov 2026
- Released
- 30 Oct 2026GitHub
- Developer
- Linux ContainersWikidata
- License
- Apache Software License 2.0Wikidata
- Written in
- GoWikidata
- First released
- 7 Aug 2023Wikidata
- First published on GitHub
- 22 Jul 2023GitHub
Vulnerabilities in Incus
- In our list
- 92
- Published in the last 12 months
- 89
- Critical, last 12 months
- 37
- High, last 12 months
- 28
- Known exploited
- 0
- CVE-2026-130786Incus before 7.6.0 LXC Configuration Injection via OCI Image ConfigCritical 9.4 18 Nov 2026
- CVE-2026-130785Incus 7.3.0 before 7.6.0 Guest API Container Impersonation via Forged CgroupHigh 8.4 18 Nov 2026
- CVE-2026-130784Incus before 7.6.0 Authorization Bypass via Default Project Resource InheritanceCritical 9.4 18 Nov 2026
- CVE-2026-130783Incus before 7.6.0 Token Exposure and Missing Authorization via Operation EventsCritical 9.3 18 Nov 2026
- CVE-2026-130782Incus before 7.6.0 Improper Authorization Exposes Default Project ResourcesHigh 8.3 18 Nov 2026
- CVE-2026-130781Incus before 7.6.0 Memory Exhaustion via S3 Listener Pre-Authentication BufferingHigh 7.1 18 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-63125
- GitHub Advisory Database https://github.com/advisories/GHSA-6rqx-22hc-qm36
- github.com https://github.com/lxc/incus/security/advisories/GHSA-6rqx-22hc-qm36