GPU VulnDB

Database/Container, Kubernetes & orchestration

Kyverno: namespaced PolicyExceptions fold into generated ValidatingAdmissionPolicies, bypassing enforcement

CVSS 8.3CVE-2026-122307Container, Kubernetes & orchestrationcurated

Impact

The admissionpolicygenerator controller folds PolicyExceptions into the ValidatingAdmissionPolicies it generates while ignoring the --enablePolicyException, --exceptionNamespace and policy-kind gates that are supposed to limit them. A tenant with namespaced create rights on PolicyException can inject negated matchConditions and get violating resources admitted, defeating cluster-wide enforcement. On a GPU cluster the policies this bypasses are usually the ones that matter most: blocking privileged containers, hostPath mounts, host networking, or unrestricted access to /dev/nvidia* devices - the controls that keep one tenant's pod off another tenant's GPUs and off the host. This is an enforcement bypass, not a denial of service, so it is silent until someone audits what was admitted.

Who can reach it

Any authenticated tenant with create rights on PolicyException objects in a namespace. Authentication required; exploitable from inside a tenant namespace even where the operator believed exceptions were disabled.

What to do

Upgrade Kyverno to 1.19.2 or later and restart the Kyverno pods. In the meantime, remove namespaced create rights on PolicyException from tenant roles and audit existing PolicyException objects and generated ValidatingAdmissionPolicies for injected matchConditions. Control-plane only - no node maintenance.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.