CVE-2026-106096

Cri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes

Published Nov 18, 2026 CVSS 3.1 · 6.4 Medium EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A flaw in CRI‑O allows a container using the optional Linux LinkLogs feature to create a symlink to a host log file even though the bind mount is intended to be read‑only. When conmon later appends log data, attacker‑controlled data is written to the host file, corrupting the integrity of audit logs. The vulnerability does not provide remote code execution; it is limited to tampering with host logs that conmon can write to.

Affected Systems

Red Hat OpenShift Container Platform versions 4 (specifically 4.15 and later) and 5, with CRI‑O running on the cluster nodes. The issue is present when the LinkLogs feature is enabled, which is not the default configuration.

Risk and Exploitability

The CVSS score of 6.4 indicates moderate severity. The EPSS value is unavailable, and the vulnerability is not listed in CISA’s KEV catalog. An attacker needs to run a non‑privileged container that can assume UID 0, have the LinkLogs feature enabled, and have an existing host log file that conmon can append to. The attack path is succinct: create a symlink in the pod to a future kubelet log path, then trigger conmon to write to the log, thereby inserting attacker data. While the exploit does not provide full control over the host, it compromises the integrity of audit and diagnostic logs, potentially hiding malicious activity and undermining forensic investigations.

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.


OpenCVE Recommended Actions

  • Keep OpenShift’s default Security Context Constraints; do not grant anyuid, privileged, or other SCCs that allow containers to run as UID 0 to untrusted projects.
  • Review and revise existing SCC grants to identify and remove namespaces or service accounts that map to UID 0.
  • Disable or remove the LinkLogs feature in CRI‑O configuration to prevent bind mounts that can be improperly written to.

Generated by OpenCVE AI on November 18, 2026 at 06:04 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
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'}

Weaknesses
  • CWE-59

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

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Nov 18, 2026, 1:58 AM
Reserved
Oct 6, 2026, 3:25 PM
Status
Awaiting Analysis
Published
Nov 18, 2026, 2:17 AM
Modified
Nov 18, 2026, 2:17 AM