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
Affects kyvernoSource GCVE Database
Not known to be exploited · CVSS 7.7 High · fixed in 1.19.1 : patch kyverno soon.
Data as of 11 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.19.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubkyverno/kyvernopkg:github/kyverno/kyvernoOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.