In Kata Containers configurations that use genpolicy for Confidential Containers guest protection, insufficient validation of CreateContainer mount and storage rules allows a malicious host operator to craft CreateContainer requests that cause arbitrary container-rootfs paths to be mounted over host-provided locations (such as /etc/hostname, /etc/hosts, /etc/resolv.conf, Kubernetes/Azure service-account token paths, and other volume mounts), or to provision arbitrary content under /dev/shm and /dev/termination-log. Applications that treat those paths as non-sensitive or guest-only may expose confidential information or accept attacker-controlled input. Standard Kata sandboxing is not affected.