Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
Red Hat OpenShift's default restricted / restricted-v2 SCCs do not allow containers to run as UID 0. That blocks the tested attack, even though LinkLogs is allowed in CRI-O on 4.15 and later.SELinux is enforcing on OpenShift nodes and further limits which host files conmon can write. Do not disable SELinux. Until a fixed cri-o build is installed, customers should: 1. Keep default SCCs. Do not grant anyuid, privileged, or other SCCs that allow host UID 0 to untrusted projects. 2. Review existing grants. Find namespaces/SAs that can run as UID 0.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 18 Nov 2026 02:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in CRI-O. When the optional Linux LinkLogs feature is enabled, the host pod log directory is bind-mounted into a pod emptyDir and is intended to be read-only, but Linux ignores MS_RDONLY on the initial bind and the CRI mount stays writable. A non-privileged UID 0 container can place a symlink at a future kubelet log path so that privileged conmon later appends attacker-controlled log data to an existing host file. This is an append-only host integrity issue, not universal remote code execution; LinkLogs is not enabled by default. | |
| Title | Cri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes | |
| First Time appeared |
Redhat
Redhat openshift |
|
| Weaknesses | CWE-59 | |
| CPEs | cpe:/a:redhat:openshift:4 cpe:/a:redhat:openshift:5 |
|
| Vendors & Products |
Redhat
Redhat openshift |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-11-18T01:58:28.544Z
Reserved: 2026-10-06T15:25:28.162Z
Link: CVE-2026-106096
No data.
Status : Awaiting Analysis
Published: 2026-11-18T02:17:39.110
Modified: 2026-11-18T02:17:39.233
Link: CVE-2026-106096
No data.
OpenCVE Enrichment
No data.