CVE-2026-23953: Incus container environment configuration newline injection
Summary A user with the ability to launch a container with a custom YAML configuration (e.g a member of the ‘incus’ group) can create an environment variable containing newlines, which can be used to add additional configuration items in the container’s lxc.conf due to the newline injection. This can allow adding arbitrary lifecycle hooks, ultimately resulting in arbitrary command execution on the host.
Details When passing environment variables in the config block of a new container, values are not checked for the presence of newlines [1], which can result in newline injection inside the generated container lxc.conf. This can be used to set arbitrary additional configuration items, such as lxc.hook.pre-start. By exploiting this, a user with the ability to launch a container with an arbitrary config can achieve arbitrary command execution as root on the host.
Exploiting this issue on IncusOS requires a slight modification of the payload to change to a different writable directory for the validation step (e.g /tmp). This can be confirmed with a second container with /tmp mounted from the host (A privileged action for validation only).
[1] https://github.com/lxc/incus/blob/HEAD/internal/server/instance/drivers/driverlxc.go#L1081
PoC A proof-of-concept script exploiting this vulnerability can be found attached, named environmentnewlineinjection.sh, showing arbitrary command execution, which will write a file to the root filesystem (/newlineinjectioncommandexecpoc)
Manual Reproduction steps: 1. Launch a new container with a configuration file containing a multiline YAML string as an environment variable value, such as in the listing below. 2. Observe that the lxc.conf (/run/incus/user-1000poc/lxc.conf in my case) contains an additional lxc.hook.pre-start item 3. Observe the creation of the file in the host root directory, with contents proving command execution as root.
incus launch images:alpine/edge --ephemeral poc << EOF config: environment.FOO: |- abc lxc.hook.pre-start = /bin/sh -c "id > /newlineinjectioncommandexecpoc" EOF
Impact A user with the ability to launch a container with a custom YAML configuration (e.g a member of the ‘incus’ group) can achieve arbitrary command execution on the host.
Attachments environmentnewlineinjection.sh environmentnewlineinjection.patch
Other sources
Incus is a system container and virtual machine manager. In versions 6.20.0 and below, a user with the ability to launch a container with a custom YAML configuration (e.g a member of the ‘incus’ group) can create an environment variable containing newlines, which can be used to add additional configuration items in the container’s lxc.conf due to newline injection. This can allow adding arbitrary lifecycle hooks, ultimately resulting in arbitrary command execution on the host. Exploiting this issue on IncusOS requires a slight modification of the payload to change to a different writable directory for the validation step (e.g /tmp). This can be confirmed with a second container with /tmp mounted from the host (A privileged action for validation only). A fix is planned for versions 6.0.6 and 6.21.0, but they have not been released at the time of publication.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23953?
CVE-2026-23953 is considered a medium severity vulnerability due to the potential for unauthorized configuration manipulation.
How do I fix CVE-2026-23953?
To fix CVE-2026-23953, update the Incus package to version 6.0.6 or later, or between versions 6.20.0 and 6.1.0.
Who is affected by CVE-2026-23953?
Users with the ability to launch containers using a custom YAML configuration, specifically members of the 'incus' group, are affected by CVE-2026-23953.
What kind of attack can CVE-2026-23953 enable?
CVE-2026-23953 can enable an attacker to introduce malicious additional configuration items through newline injection in environment variables.
Is there a published advisory for CVE-2026-23953?
Yes, there is a published advisory for CVE-2026-23953 detailing the vulnerability and its implications.