CVE-2026-122311
Description
A flaw was found in Kyverno. An authenticated user with permission to create namespace-scoped policies can exploit this flaw to achieve privilege escalation and complete cluster compromise. Due to insufficient validation of path segments in resource request arguments within Common Expression Language (CEL) policies, path traversal sequences allow requests to bypass namespace boundaries. An attacker can leverage this weakness to read and modify arbitrary cluster resources using the admission controller's elevated service account credentials.
Statement
In standard Red Hat OpenShift deployments, this vulnerability is evaluated as Important because an authenticated tenant able to create policy rules can escape namespace boundaries and abuse privileged admission controller credentials to achieve full cluster compromise. Red Hat does not ship or support Kyverno in default platform installations, relying instead on built-in Kubernetes admission controls and supported policy frameworks. Consequently, standard Red Hat environments are not directly affected unless this third-party policy engine is manually installed and configured for self-service tenant access. 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)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.