# CVE-2026-76061: Cri-o: cri-o: bind_mount_prefix intermediate-symlink prefix bypass

> Attackers can bypass bind mount prefixes via symlinks to access host files or escalate privileges in CRI-O environments.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** AZL-106655

## What is CVE-2026-76061?

CVE-2026-76061 is a medium-severity path traversal vulnerability in Red Hat OpenShift Container Platform 4, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-76061?


## How do I fix CVE-2026-76061?

No fix has been published for CVE-2026-76061 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76061 being exploited?

There is no known exploitation of CVE-2026-76061 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76061 and fix it if it is affected.

What it is: CVE-2026-76061 is a medium-severity path traversal vulnerability in Red Hat OpenShift Container Platform 4, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76061 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Container Platform 4. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76061/ (Markdown: https://insights.sbomify.com/CVE-2026-76061/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76061
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76061
- OSV: https://osv.dev/vulnerability/CVE-2026-76061

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76061/
Summaries are generated and may contain mistakes; the official description above is the record.