Kyverno prior to version 1.19.2 does not correctly filter the context.apiCall urlPath after sanitization. An attacker who can create a namespace‑scoped Policy can embed directory traversal sequences, such as "../" after a URL fragment or query string, which the Kubernetes client discards, allowing the raw path to reach cluster‑scoped endpoints when executed by Kyverno's ServiceAccount. This flaw enables a legitimate user in any namespace with Policy creation rights to effectively gain cluster‑administrator privileges.

Kyverno, version 1.19.1 and earlier (i.e., any release before 1.19.2). The issue affects all deployments that expose the Policy API, including clusters running the default Kyverno service account with elevated cluster rights. Users should verify that their Kyverno installation is not within this version range.

The vulnerability carries a CVSS score of 9.4, indicating critical risk. EPSS is not available, and the flaw is not listed in CISA KEV. An attacker only needs to create a Policy object in a namespace, which can be performed by many legitimate users, so the exploit is likely feasible in environments with broad Policy‑creation permissions. Because the attack escalates privilege from a namespace context to cluster scope, it presents a high likelihood of severe impact in the right circumstances.