CVE-2026-122307 · Package
NO FIX YET · SEE WHAT TO DO
Kyverno before 1.19.2 folds PolicyExceptions into generated ValidatingAdmissionPolicies while ignoring its own enablement and namespace gates. A user with namespaced create rights on PolicyExceptions can inject negated matchConditions, so violating resources are admitted despite cluster-wide enforcement.
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 below 1.19.2 where some users can create PolicyException resources in a namespace. Clusters without Kyverno, or where PolicyException creation is restricted to trusted admins, are less exposed. Teams that do not use the admission policy generator controller should still confirm the version.
Not affected if kyverno-1.19.2-or-later, no-policyexception-create-rights
Who cares kubernetes, kyverno, policy-as-code
kubectl get deploy -n kyverno kyverno-admission-controller -o jsonpath='{.spec.template.spec.containers[0].image}'kubectl auth can-i create policyexceptions -n <namespace> across namespaces1.19.2 or later (fixed version from the advisory)Kyverno before 1.19.2 contains a policy bypass vulnerability in the admissionpolicygenerator controller, which folds PolicyExceptions into generated ValidatingAdmissionPolicies while ignoring the --enablePolicyException, --exceptionNamespace, and policy kind gates. Users with namespaced create rights on PolicyExceptions can inject negated matchConditions into the generated policies to admit violating resources, bypassing cluster-wide enforcement.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/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.