Kyverno versions 1.16.0 through 1.19.0 register a global CEL library, globalcontext.Lib, in policies without constraining it to the policy's namespace. A tenant who can create any namespaced policy can invoke globalContext.get("<entry>", "") to retrieve the entire cached contents of a cluster‑scoped GlobalContextEntry. The returned data may include resources from namespaces the attacker has no RBAC permission to read, exposing sensitive cluster state. This flaw is a classic information‑exposure weakness (CWE‑200) and can lead to a breach of confidentiality for all cluster resources.

The vulnerability affects Kyverno deployments of any version between 1.16.0 and 1.19.0 inclusive. The affected product is Kyverno, the Kubernetes policy engine provided by the Kyverno project. Users running these versions in any namespace are potentially exposed.

The CVSS score of 8.3 classifies the issue as high severity. EPSS data is unavailable, but because the exploit requires only the ability to create a namespaced policy – a capability many cluster tenants already possess – the likelihood of exploitation in active environments is significant. The vulnerability is not yet listed in CISA KEV, however the attack vector is local to the cluster, making it a valuable target for poorly secured workloads.