Kyverno before 1.19.2 Cross-Namespace Resource Read via generate.clone
Kyverno before 1.19.2 lets namespaced Policy authors that template generate.clone or cloneList read ConfigMaps from other namespaces. Fixed in 1.19.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.19.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The vulnerable policy is a namespaced Policy that templates generate.clone or cloneList namespace values Background-controller RBAC grants get/list/watch on configmaps and namespaces cluster-wide, so the read succeeds against any namespace by default
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.21% · 11th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Kyverno, a Kubernetes policy engine, is affected by a flaw that lets an attacker with low-privilege access, such as a namespaced Policy author, read sensitive resources like ConfigMaps from other namespaces, including those belonging to other tenants. The attacker can reach it remotely over the network, and the attack requires low-privilege login but no user interaction.
Read the original description
Kyverno before 1.19.2 contains a missing authorization vulnerability that allows namespaced Policy authors to read resources in other namespaces by templating generate.clone or cloneList namespace values. Attackers can annotate a triggering ConfigMap so the background-controller copies a victim namespace's sensitive ConfigMap into the attacker's namespace, enabling cross-tenant data disclosure.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The vulnerable policy is a namespaced Policy that templates generate.clone or cloneList namespace values Background-controller RBAC grants get/list/watch on configmaps and namespaces cluster-wide, so the read succeeds against any namespace by defaultUpgrade to a fixed version: 1.19.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- kyverno kyverno
fixed in 1.19.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122320
Is CVE-2026-122320 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A namespaced Kyverno Policy can use generate.clone or cloneList to have the background controller copy ConfigMaps from other namespaces into the policy's own namespace. The controller's cluster-wide read permissions let the copy succeed by default, which exposes data across namespace boundaries.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-122320?
kyverno: before 1.19.2.Source: cve.now feed data
Am I affected, and how do I check?
Kyverno versions before 1.19.2 are affected, and the issue is limited to namespaced Policy resources that template generate.clone or cloneList namespace values. To check, run kyverno version or inspect the controller image tag, then search namespaced Policies for generate.clone or cloneList.Source: vulncheck.com, github.com
How do I fix CVE-2026-122320?
Upgrade Kyverno to 1.19.2 or later. The checked facts list no workaround, so the fix version is the only documented remedy.Source: vulncheck.com, github.com