CVE-2026-76061

Cri-o: cri-o: bind_mount_prefix intermediate-symlink prefix bypass

  • Medium 5.5

Description

A flaw was found in CRI-O's `bind_mount_prefix` handling. When configured with a non-empty `bind_mount_prefix`, a malicious container or local attacker could use a Container Runtime Interface (CRI) hostPath containing an intermediate absolute symlink. This could cause the bind mount source to resolve outside the intended prefixed root, potentially leading to unauthorized access to files or privilege escalation on the host system.

Key facts

Published
6 Oct 2026
Last changed
18 Nov 2026
Assigned by
redhat
EPSS
0.23% likely to be exploited in the next 30 days, higher than 13.921% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.5CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected

Timeline

  1. 13 Aug 2026 Reported to Red Hat.
  2. 21 Sep 2026 Made public.
  3. 6 Oct 2026 Published

Weakness

References