Security readout for executives and security teams
Plain-English summary
CVE-2026-23953 lets an authorized Incus user turn container configuration input into host-level command execution. This is not a remote unauthenticated bug; it requires the ability to launch containers with custom YAML configuration, such as incus group membership. For shared container hosts, this is a serious privilege-boundary issue.
Executive priority
Prioritize this for any shared Incus host or environment where non-root users can create containers. The business risk is host compromise from a user who should only control containers. Single-admin lab systems are lower urgency but should still track the vendor fix.
Technical view
Incus versions 6.20.0 and below mishandle newlines in environment variable values from custom YAML. The newline injection can add unintended lxc.conf entries, including lifecycle hooks, which can lead to arbitrary command execution on the host. The CVE lists CWE-93 and CVSS 8.7.
Likely exposure
Systems running lxc/incus versions 6.1.0 through 6.20.0, or 6.0.5 and earlier, are in scope if users can launch containers with custom YAML configuration. Highest exposure is multi-user Incus environments or hosts where incus group membership is broadly granted.
Exploitation context
The source bundle does not indicate known active exploitation, and KEV is false. Exploitation requires low privileges within the Incus management context, not anonymous internet access. Public references include advisory material and validation artifacts, so defenders should assume capable users can understand the issue.
Researcher notes
The advisory states fixed versions 6.0.6 and 6.21.0 were planned but unreleased at publication. Avoid relying on payload-based validation in production. Focus review on input sanitization of environment variables before lxc.conf generation and authorization boundaries around custom YAML launches.
Mitigation direction
- Inventory Incus versions and identify hosts at or below 6.20.0 or 6.0.5.
- Restrict incus group membership to trusted administrators only.
- Limit who can launch containers with custom YAML configuration.
- Monitor vendor guidance for fixed releases 6.0.6 and 6.21.0.
- Upgrade promptly when fixed versions become available.
- Review recent container launches by non-administrative Incus users.
Validation and detection
- Check installed Incus version against the affected ranges.
- Audit local users and groups with Incus launch permissions.
- Review Incus projects for custom YAML usage by untrusted users.
- Look for unexpected lifecycle hook configuration in container profiles or generated lxc.conf.
- Confirm remediation status against the official GitHub advisory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-93: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Open ATT&CK lookupContainer behavior lookup
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.
Open ATT&CK lookupCVE-2026-23953 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N2.35.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.7HighVector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/lxc/incus/security/advisories/GHSA-x6jc-phwx-hp32CVE reference · x_refsource_CONFIRM
- https://github.com/lxc/incus/blob/HEAD/internal/server/instance/drivers/driver_lxc.go#L1081CVE reference · x_refsource_MISC
- https://github.com/user-attachments/files/24473682/environment_newline_injection.shCVE reference · x_refsource_MISC
- https://github.com/user-attachments/files/24473685/environment_newline_injection.patchCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of CRLF Sequences ('CRLF Injection')
Improper Neutralization of CRLF Sequences ('CRLF Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.