PatchSiren cyber security CVE debrief
CVE-2026-88264 Red Hat CVE debrief
A flaw in crun allows terminal setup to redirect /dev/console onto an attacker-controlled path when /dev is not dedicatedly mounted in the container configuration. This issue affects crun versions 1.29.1 and earlier. Default configurations with a fresh /dev mount are not exposed. No fixed release is available yet. The issue arises from the container configuration not giving /dev a dedicated mount, allowing terminal setup to redirect /dev/console onto an attacker-controlled path, potentially impacting container security.
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 10
- CVSS
- MEDIUM 5.6
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-10
- Original CVE updated
- 2026-09-15
- Advisory published
- 2026-09-10
- Advisory updated
- 2026-09-15
Who should care
Roles responsible for container configuration and security should assess exposure and verify if /dev is dedicatedly mounted in their environments. This includes operators, platform administrators, and security teams who manage containerized systems using crun. They should review their configurations to ensure that /dev is properly mounted to prevent potential exploitation.
Why it matters
The flaw in crun allows terminal setup to redirect /dev/console onto an attacker-controlled path, potentially impacting container security.
- Assess container configurations for potential exposure
- Verify /dev mount configurations
- Monitor for exploitation attempts
Technical summary
The flaw in crun occurs when the container configuration does not give /dev a dedicated mount, allowing terminal setup to redirect /dev/console onto an attacker-controlled path. This issue affects crun versions 1.29.1 and earlier. The vulnerability arises from the interaction between crun's terminal setup and the container's /dev configuration, which can lead to a security risk if not properly managed. Affected users should assess their configurations and verify the mount settings for /dev to mitigate potential exposure.
Defensive priority
Assess exposure in container configurations using crun 1.29.1 or earlier and verify if /dev is dedicatedly mounted.
Recommended defensive actions
- Assess container configurations using crun 1.29.1 or earlier
- Verify if /dev is dedicatedly mounted
- Monitor for potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the flaw in crun and its potential impact. However, the exact scope of affected systems and remediation steps require further verification. The issue is exacerbated by the lack of a dedicated /dev mount in the container configuration, which allows for the redirection of /dev/console. Further review of container configurations and /dev mount settings is necessary to assess exposure.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-88264 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-88264
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-88264 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-88264
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/security/cve/CVE-2026-88264
-
Source reference
Unverified legacy reference
URL: https://github.com/containers/crun/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.