CVE-2026-106096 json
Cri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes
published 1h ago modified 1h ago also EUVD-2026-128410
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-106096 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-106096 updated cvss 6.4
cri-o: cri-o: Writable LinkLogs bind mount allows pods to redirect privileged conmon log writes
-
Red Hat OpenShift Container Platform 4 cri-o Red Hat OpenShift Container Platform 5 cri-oaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L |
| NVD | 3.1 | 6.4 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L |
Affected products
- Red Hat Red Hat OpenShift Container Platform 4
- Red Hat Red Hat OpenShift Container Platform 5
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
access.redhat.com
/security/cve/CVE-2026-106096
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2546703
issue-tracking
Sources
- CVE List CVE-2026-106096
- NVD CVE-2026-106096
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.