The k8saudit plugin's default rules did not inspect security-relevant settings on Kubernetes initContainers and ephemeralContainers, only regular containers. This allowed pod creators to run privileged or otherwise sensitive containers in these container types without triggering the default 'Create Privileged Pod' detection rule. The issue affects k8saudit and its cloud-provider variants. A fix was released in k8saudit 0.18.0 and corresponding cloud variants on 2026-06-19. Until upgraded, restricting pod creation and enforcing Pod Security Admission or admission controllers can mitigate risk.