Executive Summary

A critical vulnerability (CVE-2026-124441) with a CVSS score of 8.8 has been identified in Kyverno, a policy engine for Kubernetes. This vulnerability enables namespaced tenants to bypass authorization and generate any resource kind in any namespace, potentially leading to privilege escalation and unauthorized access. The affected versions are Kyverno before 1.19.2.

Technical Analysis

The vulnerability is classified as an authorization bypass issue. It allows attackers to template the generate rule's kind and namespace with variables, effectively bypassing the intended authorization mechanisms. The attack vector involves creating a Policy and triggering a ConfigMap in the attacker's own namespace, which causes the privileged background-controller to write NetworkPolicies or RoleBindings into victim or kube-system namespaces. The root cause of this vulnerability is the lack of proper input validation and authorization checks in the generate rule's processing logic.

How It Gets Exploited

An attacker with low privileges in a namespaced tenant can exploit this vulnerability. The attacker would create a Policy that triggers a ConfigMap in their own namespace. This action causes the background-controller, which runs with elevated privileges, to write arbitrary NetworkPolicies or RoleBindings into other namespaces, including kube-system. This could allow the attacker to escalate privileges, gain unauthorized access to sensitive resources, or disrupt cluster operations.

Impact Assessment

The impact of this vulnerability is significant. Successful exploitation could allow an attacker to achieve privilege escalation, unauthorized access to sensitive resources, or disruption of cluster operations. The CVSS score of 8.8 indicates a high severity level. Affected products include Kyverno versions before 1.19.2.

Recommended Actions

To mitigate this vulnerability, it is recommended to update Kyverno to version 1.19.2 or later. Additionally, users should:
  • Review and restrict the permissions of the background-controller.
  • Monitor for suspicious activities, such as unauthorized creation of NetworkPolicies or RoleBindings.
  • Implement network segmentation and least privilege principles to limit the blast radius.

Sources