CVE-2026-106096: Red Hat OpenShift Container Platform 4 · Improper Link Resolution Before File Access
Affects Red Hat OpenShift Container Platform 4Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 18 Nov 2026, 02:04 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 6.4 |
|---|
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat OpenShift Container Platform 4cri-o | Affected– | Fixed in– |
| Red Hat OpenShift Container Platform 5cri-o | Affected– | Fixed in– |
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.