{"answers":{"affected":"1 open source package ship an affected version, including kyverno.","exploited":"There is no known exploitation of CVE-2026-100703 in the wild and no public exploit code.","fix":"Upgrade kyverno to 1.19.1 or later.","what":"CVE-2026-100703 is a high-severity vulnerability in kyverno, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100703 and fix it if it is affected.\n\nWhat it is: CVE-2026-100703 is a high-severity vulnerability in kyverno, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-100703 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kyverno (Bitnami): affected from 1.16.0; fixed in 1.19.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100703/ (Markdown: https://insights.sbomify.com/CVE-2026-100703/index.md)","id":"CVE-2026-100703","markdown":"https://insights.sbomify.com/CVE-2026-100703/index.md","name":"CVE-2026-100703","record":{"aliases":["BIT-kyverno-2026-100703","GHSA-59v6-2x73-wfg4","GHSA-cmr3-jwxg-m6m3","MINI-76q7-cch4-wfpp","MINI-c953-mmv6-rgwq","MINI-hr4c-83gw-ggc8","MINI-jf2r-wvxj-jxp4","MINI-p6h6-7mm6-vwqc","MINI-r7q5-m56r-rm9g"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes policy engine","requires_auth":"low_privilege","summary":"Tenants can access cluster-scoped cached data from other namespaces via the globalcontext library, bypassing RBAC restrictions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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(\"\u003centry\u003e\", \"\") 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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Kyverno before 1.19.1 Cross-Namespace Data Access via globalcontext.Lib","id":"CVE-2026-100703","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Kyverno before 1.19.1 ImageValidatingPolicy Exception Bypass","id":"CVE-2026-100704"},"packages":[{"ecosystem":"Bitnami","fixed":["1.19.1"],"introduced":["1.16.0"],"last_affected":[],"package":"kyverno","purl":"pkg:bitnami/kyverno","source":"BIT-kyverno-2026-100703"}],"prev":{"headline":"Nodemailer before 10.0.2 Stack Exhaustion via Nested Recipient Arrays","id":"CVE-2026-100702"},"products":["kyverno"],"published":"2026-09-26","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["kyverno"]},"summary":"Tenants can access cluster-scoped cached data from other namespaces via the globalcontext library, bypassing RBAC restrictions.","url":"https://insights.sbomify.com/CVE-2026-100703/"}