CVE
Red Hat host file append via symlink in CRI-O
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
A flaw in cri-o in Red Hat OpenShift Container Platform lets a local attacker with low-privilege access append attacker-controlled data to an existing file on the host, but only when the optional LinkLogs feature is enabled, which is not the default. The attacker, using a container running as UID 0, makes a writable log mount redirect a privileged logging process's writes to that host file, and no user action is needed.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Shipped in major Linux distributions
- Severity6.4/10CVSS 6.4
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-106096 (Cri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-106096 (entry last updated 2026-11-18):
Affected:
- Red Hat Confidential Compute Attestation: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-106096 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-106096 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2546703
- https://access.redhat.com/security/cve/CVE-2026-106096
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-106096
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-106096"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- openshift-sandboxed-containers/osc-monitor-rhel9
Version range not reported
- cri-o
Version range not reported
- kata-containers
Version range not reported
- openshift4/cnf-tests-rhel8
Version range not reported
- openshift4/ztp-site-generate-rhel8
Version range not reported
- openshift/ose-rhel-coreos-8
Version range not reported
- openshift/ose-rhel-coreos-9
Version range not reported
- cri-o
Version range not reported
- kata-containers
Version range not reported
- openshift/ose-rhel-coreos-9
Version range not reported
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-106096 |
| Record | NVD · CVE-2026-106096 |
| Write-ups 1Establishes: Technical detail and context. | |
| Report | bugzilla.redhat.com · show_bug.cgi?id=2546703 |
| Other links 1 | |
| Link | access.redhat.com · security/cve/CVE-2026-106096 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.