CRI-O Linux LinkLogs writable bind mount privilege escalation
CVE-2026-106096 Published on November 18, 2026

Cri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes
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.

NVD

Vulnerability Analysis

CVE-2026-106096 is exploitable with local system access, and requires small amount of user privileges. This vulnerability is consided to have a high level of attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality, a high impact on integrity, and a small impact on availability.

Attack Vector:
LOCAL
Attack Complexity:
HIGH
Privileges Required:
LOW
User Interaction:
NONE
Scope:
CHANGED
Confidentiality Impact:
NONE
Integrity Impact:
HIGH
Availability Impact:
LOW

Timeline

Reported to Red Hat.

Made public. 42 days later.

Weakness Type

What is an insecure temporary file Vulnerability?

The software attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

CVE-2026-106096 has been classified to as an insecure temporary file vulnerability or weakness.


Products Associated with CVE-2026-106096

Want to know whenever a new CVE is published for Red Hat Openshift? stack.watch will email you.

Affected Versions

Red Hat OpenShift Container Platform 4: Red Hat OpenShift Container Platform 5: