GPU VulnDB

Database/Container, Kubernetes & orchestration

Kyverno: namespaced CleanupPolicy context entries run with the cleanup controller's ServiceAccount

CVSS 9.4CVE-2026-122304Container, Kubernetes & orchestrationcurated

Impact

In Kyverno 1.17.0 through 1.19.1 the cleanup controller builds its context loader with a nil policy, so namespace confinement is never applied to context entries. A namespace admin can create a namespaced CleanupPolicy whose apiCall or globalReference context entries run with the cleanup controller's own ServiceAccount, reading Secrets in other namespaces and modifying validatingwebhookconfigurations. Disabling or rewriting a validating webhook configuration is the step that precedes everything else on a shared GPU cluster: it switches off the admission checks that stop privileged pods and host device mounts, after which a tenant can ask for the host directly. This is a separate flaw from the mutate-existing target bypass (CVE-2026-122303) in the same release, with its own controller and its own advisory.

Who can reach it

Authenticated namespace admin who can create a CleanupPolicy in a namespace they control; no cluster-scoped permissions needed.

What to do

Upgrade Kyverno to 1.19.2 and restart the cleanup controller deployment. In the interim remove tenant RBAC for namespaced CleanupPolicy objects, review existing CleanupPolicies for apiCall and globalReference context entries, and verify that no validatingwebhookconfiguration has been altered.

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.