CVE-2026-122304

Description

A flaw was found in Kyverno. An authenticated user with namespace administrative privileges can exploit an authorization bypass in the cleanup controller by creating a namespaced cleanup policy with cross-namespace context references. Because the cleanup controller fails to enforce policy restrictions during context resolution, it executes requests using its elevated service account privileges. This flaw allows an attacker to achieve privilege escalation, read sensitive resources across namespaces, and alter cluster-wide admission configurations.

Statement

This vulnerability is rated as Important because it permits tenant-level users to completely break namespace isolation and gain cluster-wide administrative control. By exploiting unconstrained context resolution within policy cleanup routines, a tenant administrator can leverage the controller's elevated privileges to access sensitive resources across namespaces and tamper with cluster admission configurations. Red Hat OpenShift does not package or enable Kyverno by default, so standard platform deployments are unaffected unless third-party policy controllers are manually installed in the cluster. Red Hat ships Kyverno only via Konflux pipeline images; OpenShift and RHEL do not include Kyverno as a platform component. Impact for Red Hat products is therefore Important.

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data; Read Files or Directories

An attacker could bypass intended access restrictions to read sensitive data, either by reading the data directly from a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.

Integrity

Technical Impact: Modify Application Data; Modify Files or Directories

An attacker could bypass intended access restrictions to modify sensitive data, either by writing the data directly to a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.

Access Control

Technical Impact: Gain Privileges or Assume Identity; Bypass Protection Mechanism

An attacker could bypass intended access restrictions to gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.

Confidentiality,Integrity,Availability

Technical Impact: Execute Unauthorized Code or Commands

An attacker could use elevated privileges to execute unauthorized commands or code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.

Frequently Asked Questions

Want to get errata notifications? Sign up here.