CVE-2026-122313

Description

A flaw was found in Kyverno. An authenticated user with permissions restricted to a specific namespace can bypass tenant isolation boundaries to achieve cluster-wide privilege escalation. By defining a mutating policy with Common Expression Language (CEL) rules that lack namespace validation checks, an attacker can induce the privileged background controller to modify resources in other namespaces, such as administrative access bindings and security policies.

Statement

This vulnerability is rated as Important because it enables authenticated tenants with localized namespace privileges to bypass isolation boundaries and achieve cluster-wide privilege escalation. By defining policy rules with CEL expressions that target external resources, an attacker can induce the privileged background controller to alter sensitive administrative objects such as RoleBindings and network configurations. Standard Red Hat OpenShift and Red Hat Enterprise Linux releases do not include or support Kyverno, and default installations are unaffected. 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.