CVE-2026-122313 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kyverno versions from 1.17.0 before 1.19.2 let a user limited to one namespace make NamespacedMutatingPolicy target resources in other namespaces. An attacker can have the cluster-wide background controller add their own subjects to another tenant's RoleBinding or alter Roles, NetworkPolicies and ConfigMaps.
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 that use NamespacedMutatingPolicy. The exposure needs a tenant with rights in one namespace who can create policy input, so single-tenant clusters are less exposed. unknown whether the sources list other affected configurations.
Not affected if kyverno-1.19.2-or-later, kyverno-below-1.17.0, single-tenant-cluster
Who cares kubernetes, kyverno, multi-tenant
kubectl get deployment -n kyverno -o wide or the chart version in your Helm release.NamespacedMutatingPolicy resources exist with kubectl get namespacedmutatingpolicies -A.1.19.2 or later, per the affected range in the NVD entry.Kyverno from 1.17.0 before 1.19.2 contains a privilege escalation vulnerability that allows namespace-scoped tenants to modify resources in other namespaces through NamespacedMutatingPolicy targetMatchConstraints.expression CEL output lacking namespace checks. Attackers can emit a literal target such as another tenant's RoleBinding, which the cluster-wide background controller then mutates to add attacker subjects or alter Roles, NetworkPolicies, and ConfigMaps.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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.