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.
Published: 2026-11-18
Score: 6.4 Medium
EPSS: < 1% Very Low
KEV: No
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

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.

Advisories

No advisories yet.

History

Wed, 18 Nov 2026 12:30:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Moderate


Wed, 18 Nov 2026 11:15:00 +0000

Type Values Removed Values Added
First Time appeared Redhat confidential Compute Attestation
CPEs cpe:/a:redhat:confidential_compute_attestation:1
Vendors & Products Redhat confidential Compute Attestation

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

{'score': 6.4, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L'}


Subscriptions

Redhat Confidential Compute Attestation Openshift
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-11-18T13:07:56.367Z

Reserved: 2026-10-06T15:25:28.162Z

Link: CVE-2026-106096

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-18T02:17:39.110

Modified: 2026-11-18T14:17:21.503

Link: CVE-2026-106096

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-11-17T13:48:51Z

Links: CVE-2026-106096 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-11-18T13:30:22Z

Weaknesses
  • CWE-59

    Improper Link Resolution Before File Access ('Link Following')