CVE-2026-23953
BaseFortify
Publication date: 2026-01-22
Last updated on: 2026-01-30
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linuxcontainers | incus | to 6.0.5 (inc) |
| linuxcontainers | incus | From 6.1.0 (inc) to 6.21.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-93 | The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Incus versions 6.20.0 and below, where a user able to launch a container with a custom YAML configuration can inject newlines into environment variables. This newline injection allows adding extra configuration items into the container's lxc.conf file, enabling the addition of arbitrary lifecycle hooks. Ultimately, this can lead to arbitrary command execution on the host system.
How can this vulnerability impact me? :
Exploiting this vulnerability can allow an attacker with limited privileges (a user able to launch containers with custom YAML) to execute arbitrary commands on the host system. This can compromise the host's security, potentially leading to unauthorized access, data manipulation, or disruption of services.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting the ability to launch containers with custom YAML configurations to trusted users only (e.g., limiting membership of the 'incus' group), avoiding running vulnerable versions (6.20.0 and below), and monitoring for updates or patches, specifically versions 6.0.6 and 6.21.0 once released. Additionally, avoid mounting writable host directories like /tmp into containers for validation purposes until a fix is applied.