5 matches found
BIT-KYVERNO-2026-100703 Kyverno before 1.19.1 Cross-Namespace Data Access via globalcontext.Lib
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...
PT-2026-105110
Kyverno before 1.19.1 contains a namespace isolation bypass in the apiCall context entry of namespaced Policy resources due to inconsistent path interpretation between validation and execution. A low-privilege tenant can use percent-encoded dot-segments in urlPath to bypass namespace checks and...
PT-2026-105106
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...
CVE-2026-100703
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...
CVE-2026-100703
Kyverno versions 1.16.0 through 1.19.0 are vulnerable to a cross-namespace data access issue due to the improper registration of the globalcontext.Lib CEL library . Unlike other sibling libraries, this component is not confined to the policy's namespace. A tenant with permissions to create a name...