Answer in brief
CVE-2026-100703 records a High severity (CVSS 8.3) vulnerability in Kyverno before 1.19.1 Cross-Namespace Data Access via globalcontext.Lib. The current sources do not mark it as known exploited. The current feed maps kyverno/kyverno (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps kyverno/kyverno (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| kyverno/kyvernogeneric | >=1.16.0 <1.19.1 | 1.19.1 |
Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 26, 2026
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.
Quoted source text, attributed separately from HOL analysis.