The CRI checkpoint import process fails to validate image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force the system to pull a malicious image and assign it an arbitrary local tag, poisoning the node's local image cache. If other pods on the same node use the poisoned tag with an `IfNotPresent` or `Never` pull policy, they will execute the malicious image instead of the legitimate one, allowing the attacker to execute arbitrary code under the victim pod's identity. Additionally, some related issues can lead to host-root command execution during restore.