CVE-2026-122316 · Runtime
NO FIX YET · SEE WHAT TO DO
Kyverno's mutate-existing background processor lacks an authorization check, so a namespace tenant can create a NamespacedMutatingPolicy that changes objects in other namespaces. The attack makes the background-controller service account strip Pod Security labels cluster-wide.
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 up to but not including 1.19.2 where namespace tenants can create NamespacedMutatingPolicy resources. The flaw lets a tenant reach objects outside their own namespace and strip Pod Security labels cluster-wide. Clusters with no multi-tenant namespace access or a patched Kyverno can skip it.
Not affected if kyverno-1.19.2-or-later, single-tenant-cluster
Who cares kubernetes, kyverno, multi-tenant
kubectl get deploy -n kyverno -o jsonpath='{.items[*].spec.template.spec.containers[*].image}'kubectl get namespacedmutatingpolicies -A and review which tenants can create them1.19.2 or later (the sources state fixed versions from 1.17.0 before 1.19.2)Kyverno from 1.17.0 before 1.19.2 contains a missing authorization vulnerability in the mutate-existing background processor that allows namespaced tenants to modify resources outside their namespace. Attackers can create a NamespacedMutatingPolicy targeting Namespace objects or victim-namespace resources via CEL expressions, making the background-controller ServiceAccount strip Pod Security labels cluster-wide.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
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.