CVE-2026-122303

Description

A flaw was found in Kyverno. An authenticated user with limited, namespace-level permissions can bypass multi-tenancy isolation boundaries by crafting a mutating policy that targets other namespaces. Because the privileged background controller applies these policies without validating namespace boundaries, an attacker can modify arbitrary cluster resources, such as sensitive credentials and application deployments, in other tenants' environments. This can lead to cluster-wide privilege escalation and unauthorized control over the entire cluster.

Statement

This vulnerability is rated as Important because it enables authenticated namespace users to bypass multi-tenancy isolation boundaries and overwrite arbitrary resources cluster-wide, resulting in complete compromise of cluster integrity and confidentiality. Red Hat Enterprise Linux and Red Hat OpenShift Container Platform do not ship or support Kyverno, as OpenShift relies on native admission controllers and supported policy frameworks. Consequently, default Red Hat environments are not affected, though any cluster running Kyverno with delegated namespace-level policy management remains susceptible to privilege escalation through the controller's elevated service account. 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.