GPU VulnDB

Database/Container, Kubernetes & orchestration

Kyverno: NamespacedMutatingPolicy target expressions lack namespace checks, enabling cross-namespace mutation

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

Impact

CEL output from a NamespacedMutatingPolicy's targetMatchConstraints.expression is not checked against the policy's own namespace. A tenant can emit a literal target naming another tenant's object, and the cluster-wide background controller mutates it - adding attacker subjects to a RoleBinding, or rewriting Roles, NetworkPolicies and ConfigMaps. On a shared GPU cluster that is a direct path into another tenant's namespace: grant yourself a binding there, then read its secrets and run workloads against its quota and its GPUs. Rewriting NetworkPolicies also means tenant isolation on the fabric can be quietly loosened without the victim seeing a change they made.

Who can reach it

An authenticated namespace-scoped tenant who can create a NamespacedMutatingPolicy. Kubernetes API access only.

What to do

Upgrade Kyverno to 1.19.2 or later (affects 1.17.0 onwards) per the GitHub advisory. Controller rollout and pod restart, no node drain. Interim: prevent tenants from creating NamespacedMutatingPolicy objects, and audit RoleBindings and NetworkPolicies in tenant namespaces for unexpected mutations.

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.