CVE-2026-122320: Kyverno before 1.19.2 Cross-Namespace Resource Read via generate.clone

Published Nov 5, 2026

Updated

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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade Kyverno to a version that resolves this vulnerability.
Fixed in 1.19.2

Event History

Nov 5, 2026

CVE Published

via MITRE·02:25 AM

Data Sourced

via MITRE·02:25 AM

DescriptionSeverityWeakness

Data Sourced

via NVD·03:17 AM

DescriptionSeverityWeakness

Frequently Asked Questions

What access does an attacker need to exploit this issue?

The attacker must be able to author a namespaced Kyverno Policy and annotate a triggering ConfigMap. They can then template the namespace used by generate.clone or cloneList to target a resource in another namespace.

Which environments are most exposed?

Clusters running Kyverno before 1.19.2 are exposed where namespaced Policy authors can cause the background-controller to process a triggering ConfigMap. The impact is greatest when other namespaces contain sensitive ConfigMaps that the attacker could cause to be copied into their own namespace.

What is the available remediation?

Upgrade Kyverno to version 1.19.2 or later. The provided information does not identify a configuration-only mitigation for affected versions.

CVE-2026-122320: Kyverno before 1.19.2 Cross-Namespace Resource Read via generate.clone

Remediation

Event History

Frequently Asked Questions

What access does an attacker need to exploit this issue?

Which environments are most exposed?

What is the available remediation?

Company

Resources

Contact

Frequently Asked Questions

What access does an attacker need to exploit this issue?

Which environments are most exposed?

What is the available remediation?