Information Disclosure in Kyverno (CVE-2026-100703)
Summary
Vulnerability in Kyverno (CVE-2026-100703). Confidential information can be exposed externally. Mitigation: upgrade to 1.19.1 or later.
Original description
The description as published by the source.
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("", "") 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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-100703 has been found in Kyverno.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade Kyverno to 1.19.1 or later.
If unsure, ask your IT team or search "Kyverno CVE-2026-100703" on the vendor's site.
CVE-2026-100703 (Kyverno) — CWE-200 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.19.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in Kyverno.
Check the vendor advisory for the affected versions of Kyverno.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 1.19.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Kyverno' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Kyverno' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Kyvernoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Kyverno to 1.19.1ステージング環境で 1.19.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com