Quick answers
- Is CVE-2026-76061 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76061 being exploited in the wild.
- How severe is CVE-2026-76061?
- Medium severity, with a CVSS score of 5.5, published 6 October 2026.
- Which products and versions are affected?
- CRI-O CRI-O.
- Is there a fix for CVE-2026-76061?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-76061 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-76061?
- Check whether you run CRI-O. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
CRI-O's bind_mount_prefix feature fails to properly validate intermediate absolute symlinks in hostPath volume mounts, allowing symlink traversal attacks. An attacker with container or local host access can craft a hostPath with an intermediate symlink that resolves outside the prefixed root directory, bypassing namespace isolation. The vulnerability requires the bind_mount_prefix to be explicitly configured (non-empty), and grants file access or privilege escalation on the host.
Affected products
- CRI-O CRI-O
Timeline
- 2026-10-06: disclosed