CVE-2026-33945: Incus has an abitrary file write through its systemd-creds options
Summary Incus instances have an option to provide credentials to systemd in the guest. For containers, this is handled through a shared directory. An attacker can use the name of a systemd credential to escape that directory and overwrite arbitrary files on the host system. This can in turn be used to perform local privilege escalation or cause a DoS.
Published Mar 27, 2026
Affected packages
github.com/lxc/incus/v6
- Ecosystem
- Go
- Affected
- < 6.23.0
- Fixed in
- 6.23.0
- Check
go list -m github.com/lxc/incus/v6
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Incus instances have an option to provide credentials to systemd in the guest. For containers, this is handled through a shared directory. An attacker can use the name of a systemd credential to escape that directory and overwrite arbitrary files on the host system.
This can in turn be used to perform local privilege escalation or cause a DoS.
Details
An attacker can set a configuration key named something like systemd.credential.../../../../../../root/.bashrc to cause Incus to write outside of the credentials directory associated with the container. This makes use of the fact that the Incus syntax for such credentials is systemd.credential.XYZ where XYZ can itself contain more periods.
While it's not possible to read any data this way, it's possible to write to arbitrary files as root, enabling both privilege escalation and denial of service attacks.
Credit
This issue was discovered and reported by the team at 7asecurity
Credited to stgraber, grmpyninja, stamparm.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology