CVE-2026-122308 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kyverno before 1.19.2 trusts internal generate.kyverno.io labels on ConfigMaps, so a user with create or update rights can forge them. The forged labels make a synchronized generate policy copy sensitive Secrets from restricted namespaces into the attacker's own namespace.
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 versions before 1.19.2 that use generate policies with synchronization. Exposure depends on users who can create or update ConfigMaps in their own namespace and on Secrets that exist in restricted namespaces. Clusters on 1.19.2 or later, or without Kyverno generate policies, are not affected by this description.
Not affected if kyverno-1.19.2-or-later, no-synchronized-generate-policies
Who cares kubernetes, kyverno, multi-tenant-clusters
kubectl get deploy kyverno-admission-controller -n kyverno -o jsonpath='{.spec.template.spec.containers[0].image}'synchronize: true (kubectl get clusterpolicy -o yaml)1.19.2 or laterKyverno before 1.19.2 contains an authorization bypass vulnerability in the Generation Handler that allows users with create/update permissions to trigger synchronized generate policies by spoofing internal generate.kyverno.io labels. Attackers can label a ConfigMap as managed-by kyverno with crafted policy, rule, and trigger labels to clone sensitive Secrets from restricted namespaces into their own namespace.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/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.