CVE-2026-106096
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.
Statement
Red Hat OpenShift Container Platform and OpenShift 5 ship cri-o, and from OpenShift 4.15 the default CRI-O configuration allows the LinkLogs annotation. This flaw is not exploitable in the default OpenShift security model. Default restricted and restricted-v2 Security Context Constraints do not allow containers to run as UID 0, which is required for the attack and SELinux enforcing on the node further limits host-file writes by conmon. Customers who have not granted anyuid, privileged or equivalent SCCs to untrusted projects do not need an emergency change; apply the cri-o update when it is released through the usual RHSA.
Mitigation
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.4 | N/A | 6.4 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | High |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Changed | N/A | Changed |
| Confidentiality | None | N/A | None |
| Integrity Impact | High | N/A | High |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L
cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L
Understanding the Weakness (CWE)
Confidentiality,Integrity,Access Control
Technical Impact: Read Files or Directories; Modify Files or Directories; Bypass Protection Mechanism
An attacker may be able to traverse the file system to unintended locations and read or overwrite the contents of unexpected files. If the files are used for a security mechanism then an attacker may be able to bypass the mechanism.
Other
Technical Impact: Execute Unauthorized Code or Commands
Windows simple shortcuts, sometimes referred to as soft links, can be exploited remotely since a ".LNK" file can be uploaded like a normal file. This can enable remote execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.