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,… (CVE-2026-100703)
Kyverno versions 1.16.0 through 1.19.0 have a vulnerability where the globalcontext.Lib CEL library is registered in the policy environment without namespace confinement. This allows a tenant with permission to create namespaced policies to access cached cluster-scoped global context entries, including data from namespaces they do not have RBAC permissions to read. The issue is fixed in version 1.19.1.
AI Analysis
Technical Summary
Kyverno 1.16.0 through 1.19.0 improperly registers the globalcontext.Lib CEL library globally in its policy environment, unlike other libraries that are confined to the policy's namespace. This flaw enables a tenant who can create namespaced policies to invoke globalContext.get("<entry>", "") and retrieve cached contents of cluster-scoped GlobalContextEntry objects, potentially exposing data from namespaces outside their RBAC permissions. No admission validation prevents such access. The vulnerability is addressed in Kyverno 1.19.1.
Potential Impact
An attacker with the ability to create namespaced policies can access sensitive cached data from cluster-scoped global context entries, including information from namespaces they are not authorized to read. This results in unauthorized information disclosure. The vulnerability does not impact integrity or availability.
Mitigation Recommendations
Upgrade Kyverno to version 1.19.1 or later where this issue is fixed. No other mitigations are indicated or required as the fix confines the globalcontext.Lib CEL library to the policy's namespace.
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,… (CVE-2026-100703)
Description
Kyverno versions 1.16.0 through 1.19.0 have a vulnerability where the globalcontext.Lib CEL library is registered in the policy environment without namespace confinement. This allows a tenant with permission to create namespaced policies to access cached cluster-scoped global context entries, including data from namespaces they do not have RBAC permissions to read. The issue is fixed in version 1.19.1.
CVSS v3.1
Score 7.7high
Affected software
pkg:github/kyverno/kyvernoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Kyverno 1.16.0 through 1.19.0 improperly registers the globalcontext.Lib CEL library globally in its policy environment, unlike other libraries that are confined to the policy's namespace. This flaw enables a tenant who can create namespaced policies to invoke globalContext.get("<entry>", "") and retrieve cached contents of cluster-scoped GlobalContextEntry objects, potentially exposing data from namespaces outside their RBAC permissions. No admission validation prevents such access. The vulnerability is addressed in Kyverno 1.19.1.
Potential Impact
An attacker with the ability to create namespaced policies can access sensitive cached data from cluster-scoped global context entries, including information from namespaces they are not authorized to read. This results in unauthorized information disclosure. The vulnerability does not impact integrity or availability.
Mitigation Recommendations
Upgrade Kyverno to version 1.19.1 or later where this issue is fixed. No other mitigations are indicated or required as the fix confines the globalcontext.Lib CEL library to the policy's namespace.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-cmr3-jwxg-m6m3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100703"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab89bd9f7a7c54106942020
Added to database: 09/27/2026, 04:30:17 UTC
Last enriched: 09/27/2026, 04:41:36 UTC
Last updated: 09/28/2026, 01:47:40 UTC
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.