Description
Kyverno 1.16.0 through 1.19.0 registers the globalcontext.Lib CEL library in its policy environment without confining it to the policy's namespace, unlike the sibling libraries (resource.Lib, http.Lib, configMap loader) which are handed the policy namespace. A tenant who can create a namespaced policy (e.g. NamespacedValidatingPolicy, and likewise the namespaced mutating, deleting, generating, and image-validating policy kinds) in their own namespace can call globalContext.get("<entry>", "") and receive the full cached contents of a cluster-scoped GlobalContextEntry, including data cached from namespaces the tenant has no RBAC permission to read. No admission validation rejects such calls. Fixed in 1.19.1.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| kyverno | kyverno | 1.16.0 – < 1.19.1 | 1.19.1 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Wolfi
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Wolfi rolling | kyverno-1.17 +1 | No fix yet | — |
Advisories 1
- WID-SEC-2026-3285 Kyverno: Mehrere Schwachstellen BSI CERT-Bund (WID) · Sep 27, 2026
References
- GitHub Security Advisory (GHSA-59v6-2x73-wfg4) vendor-advisory
- VulnCheck Advisory: Kyverno before 1.19.1 Cross-Namespace Data Access via globalcontext.Lib third-party-advisory