CVE-2026-122320: Kyverno missing authorization in generate.clone namespace

CVE-2026-122320 · Severity: high · CVSS 7.7 · Published 2026-11-05

Kyverno is a Kubernetes policy engine that validates and manages resources across clusters. A missing authorization check allows a namespace member to create a policy that copies sensitive data from other namespaces into their own, enabling cross-tenant data theft. An attacker can craft a ConfigMap with annotations that tricks Kyverno's background controller into cloning a victim namespace's secrets or configurations.

Technologies: Kyverno. Vendors: Kyverno.

Quick answers

Is CVE-2026-122320 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-122320 being exploited in the wild.
How severe is CVE-2026-122320?
High severity, with a CVSS score of 7.7, published 5 November 2026.
Which products and versions are affected?
Kyverno before 1.19.2.
Is there a fix for CVE-2026-122320?
Yes: fixed in 1.19.2. Until then: Restrict who can create or modify namespaced Policies to trusted administrators, and review existing generate.clone and generate.cloneList rules to ensure the namespace value is not templated from user-controlled sources. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-122320 attacked?
It is attacked over the network.
Am I affected by CVE-2026-122320?
Check whether you run Kyverno at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 1.19.2

Restrict who can create or modify namespaced Policies to trusted administrators, and review existing generate.clone and generate.cloneList rules to ensure the namespace value is not templated from user-controlled sources.

Technical details

The vulnerability is a missing authorization check (CWE-862) in generate.clone and generate.cloneList when the namespace value is templated with attacker-controlled variables. Namespaced Policies should only be able to clone resources from their own namespace, but the code substitutes the namespace value without validating it matches the policy's namespace. An attacker with Policy creation permissions in their namespace can trigger the background-controller (which has cluster-wide read RBAC) to fetch resources from any namespace and copy them into the attacker's namespace.

Affected products

  • Kyverno Kyverno before 1.19.2

Timeline

  • 2026-10-21: disclosed
  • 2026-11-05: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.