CVE-2026-76061: cri-o · Improper Link Resolution Before File Access
Affects cri-oSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium · fixed in 1.37.1 : update cri-o when convenient.
Data as of 20 Nov 2026, 17:50 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.5 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.37.1, 1.36.6, 1.35.9 +1
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade cri-o to 1.37.1, 1.36.6, 1.35.9 or 1.34.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| cri-o | Affected
| Fixed in
|
| cri-o | Affected
| Fixed in
|
| cri-o | Affected
| Fixed in
|
| cri-o | Affected
| Fixed in
|
GitHubcri-opkg:github/cri-oOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Fixed versions of CRI-O are available: 1.34.14, 1.35.9, 1.36.6, and 1.37.1. Users should upgrade to these or later versions to remediate the vulnerability. There is no indication from the vendor advisory that any other mitigations or workarounds are recommended or sufficient. Applying the official fix is the recommended course of action.
Description
CVE-2026-76061 is a vulnerability in CRI-O's bind_mount_prefix handling that allows a malicious container or local attacker to exploit an intermediate absolute symlink in a hostPath. This can cause the bind mount source to resolve outside the intended root prefix, potentially enabling unauthorized file access or privilege escalation on the host system. The issue affects multiple versions of CRI-O prior to fixed releases. A fix is available in CRI-O versions 1.34.14, 1.35.9, 1.36.6, and 1.37.1.
References
- access.redhat.com/security/cve/CVE-2026-76061 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2520330 (opens in a new tab)
- github.com/cri-o/cri-o/commit/01f90366dc8c8db0df32b4aae7fd067c1eddbb70 (opens in a new tab)
- github.com/cri-o/cri-o/commit/6d08a9a60ecfabdb3cbea0c8d698e31f1f01cb40 (opens in a new tab)
- github.com/cri-o/cri-o/commit/d6f58973acfcae93ecc039e0297fbe5f2548b46b (opens in a new tab)