Threat Intelligence Database

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.

A vulnerability in CRI-O checkpoint restore allows a user who can create a pod from a malicious checkpointed container to bypass the destination Kubernetes security context. The restored process may retain credentials, Linux capabilities, no_new_privs, and seccomp state from the checkpoint instead of enforcing the destination configuration. This can allow execution with elevated privileges across the container security boundary. Affected upstream supported versions are CRI-O 1.34 and later. Downstream Red Hat products are affected from OCP 4.17 onward. Fixes have been applied to supported branches but are not yet released. Exploitation requires permission to create a pod from a malicious checkpoint image and checkpoint restore functionality to be available.

CVE-2026-17113 is a vulnerability in CRI-O's handling of container environment variables during container creation. When a CreateContainer request provides a nil environment variable field, CRI-O uses the OCI image's environment variables without validating their format. If an environment variable lacks an '=' character, CRI-O attempts to access a non-existent array element, causing a runtime panic that crashes the crio daemon and disrupts container runtime services on the node until restarted.

A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“). This flaw allows the container to read and write to arbitrary files on the host system.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+8#cve#cve-2024-5154

A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2024-3154