Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By redhat

  2. · 43 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-106096, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1Medium6.4CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L
NVDNVD · Awaiting Analysis3.1Medium6.4CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L
EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.4.

Affected products

What to do

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.

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-106096 badge
[![CVE-2026-106096](https://cveledger.app/badge/CVE-2026-106096.svg)](https://cveledger.app/cve/CVE-2026-106096)

Record last updated .