GPU VulnDB

Database/Container, Kubernetes & orchestration

Kyverno: unvalidated configMap.namespace lets a namespace admin read ConfigMaps in any namespace

CVSS 7.7CVE-2026-41068Container, Kubernetes & orchestrationcurated

Impact

Kyverno's ConfigMap context loader accepts any value in configMap.namespace without checking it. A namespace admin can write a policy that makes Kyverno read ConfigMaps from other namespaces using Kyverno's privileged service account. In a multi-tenant cluster this bypasses RBAC: one tenant can read another tenant's configuration and the cluster's system namespaces. This is the same flaw the CVE-2026-22039 fix closed for apiCall, but in a second code path that fix did not cover.

Who can reach it

Authenticated user with namespace-admin rights, or any user allowed to create Kyverno policies in their namespace, on a cluster running an affected Kyverno.

What to do

Upgrade Kyverno to 1.17.2, which rolls its controller pods. Nodes and workloads are not affected. The record names no fixed version for the 1.16 line. Until you upgrade, limit who can create namespaced Kyverno Policy objects.

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.