CVE-2026-122304 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kyverno versions 1.17.0 before 1.19.2 let a namespace admin escape namespace limits through a namespaced CleanupPolicy. The attacker can read Secrets in other namespaces and modify validatingwebhookconfigurations using the cleanup controller's ServiceAccount.
first public Oct 21, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Clusters running Kyverno from 1.17.0 before 1.19.2 with the cleanup controller enabled are exposed. Namespace admins in those clusters can use the cleanup controller's ServiceAccount to reach across namespaces. Clusters on versions outside that range are not affected by this description.
Not affected if version-outside-range
Who cares kubernetes, kyverno
kubectl get deployment -n kyverno kyverno-cleanup-controller -o jsonpath='{.spec.template.spec.containers[0].image}' (the deployment name is unknown from the sources; confirm it in your cluster)1.17.0 and 1.19.2, not including 1.19.21.19.2 or laterKyverno from 1.17.0 before 1.19.2 contains an authorization bypass vulnerability that allows namespace admins to escape namespace confinement because the cleanup controller builds its context loader with a nil policy. Attackers can create a namespaced CleanupPolicy with apiCall or globalReference context entries to read cross-namespace Secrets and modify validatingwebhookconfigurations using the cleanup controller's ServiceAccount.
This page as .md ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.