Kyverno vulnerabilities

CVE-2016-2183 [HIGH] CWE-200 CVE-2016-2183: The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DE

CVE-2023-47630 [HIGH] CWE-345 CVE-2023-47630: Kyverno is a policy engine designed for Kubernetes. An issue was found in Kyverno that allowed an at Kyverno is a policy engine designed for Kubernetes. An issue was found in Kyverno that allowed an attacker to control the digest of images used by Kyverno users. The issue would require the attacker to compromise the registry that the Kyverno users fetch their images from. The attacker could then return an vulnerable image to the the user and leverage

CVE-2026-22039 [CRITICAL] CWE-269 CVE-2026-22039: Kyverno is a policy engine designed for cloud native platform engineering teams. Versions prior to 1 Kyverno is a policy engine designed for cloud native platform engineering teams. Versions prior to 1.16.3 and 1.15.3 have a critical authorization boundary bypass in namespaced Kyverno Policy apiCall. The resolved `urlPath` is executed using the Kyverno admission controller ServiceAccount, with no enforcement that the request is limited to the pol

CVE-2023-42815 [MEDIUM] CWE-835 CVE-2023-42815: Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno wh Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerability was in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch signatures. With such a position, the attacker could return a

CVE-2023-42814 [MEDIUM] CWE-835 CVE-2023-42814: Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno wh Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerable component in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch attestations. With such a position, the attacker could retu

CVE-2023-42813 [MEDIUM] CWE-400 CVE-2023-42813: Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno wh Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerable component in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch attestations. With such a position, the attacker could retu

CVE-2023-42816 [MEDIUM] CWE-345 CVE-2023-42816: Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno wh Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerability was in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch signatures. With such a position, the attacker could return a

CVE-2026-54523 [CRITICAL] CWE-862 CVE-2026-54523: Kyverno is a policy engine designed for cloud native platform engineering teams. From 1.18.0 until 1 Kyverno is a policy engine designed for cloud native platform engineering teams. From 1.18.0 until 1.18.2, the NamespacedMutatingPolicy CEL compiler exposes the generator library to matchConditions, allowing a namespace-scoped policy to invoke generator.apply(namespace, resources) with an arbitrary target namespace. The validation in pkg/cel/polic

CVE-2026-4789 [CRITICAL] CWE-918 CVE-2026-4789: Kyverno, versions 1.16.0 and later, are vulnerable to SSRF due to unrestricted CEL HTTP functions. Kyverno, versions 1.16.0 and later, are vulnerable to SSRF due to unrestricted CEL HTTP functions.

CVE-2026-41323 [CRITICAL] CWE-200 CVE-2026-41323: Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1 Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1.18.0-rc1, 1.17.2-rc1, and 1.16.4, Kyverno's apiCall feature in ClusterPolicy automatically attaches the admission controller's ServiceAccount token to outgoing HTTP requests. The service URL has no validation — it can point anywhere, including atta

CVE-2026-84199 [HIGH] CWE-918 CVE-2026-84199: Kyverno before 1.16.2 contains a server-side request forgery (SSRF) vulnerability in the APICall fea Kyverno before 1.16.2 contains a server-side request forgery (SSRF) vulnerability in the APICall feature. The URL field in a Policy's ServiceCall configuration is not validated, so a user with namespace-level Policy creation permissions can direct Kyverno to make HTTP requests to arbitrary internal resources (e.g., cloud metadata endpoints such as 169

CVE-2026-40868 [HIGH] CWE-922 CVE-2026-40868: Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to 1.16.4, ky Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to 1.16.4, kyverno’s apiCall servicecall helper implicitly injects Authorization: Bearer ... using the kyverno controller serviceaccount token when a policy does not explicitly set an Authorization header. Because context.apiCall.service.url is policy-controlled, th

CVE-2025-46342 [HIGH] CWE-1287 CVE-2025-46342: Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1 Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1.13.5 and 1.14.0, it may happen that policy rules using namespace selector(s) in their match statements are mistakenly not applied during admission review request processing due to a missing error propagation in function `GetNamespaceSelectorsFromNames

CVE-2026-84200 [CRITICAL] CWE-284 CVE-2026-84200: Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in e Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can

CVE-2026-84195 [HIGH] CWE-200 CVE-2026-84195: Kyverno before 1.16.4 automatically attaches the admission controller's ServiceAccount token to outb Kyverno before 1.16.4 automatically attaches the admission controller's ServiceAccount token to outbound HTTP requests in apiCall service mode without explicit authorization headers. Attackers can exfiltrate the token by directing apiCall requests to external or attacker-controlled endpoints, gaining full control over Kyverno policies and cluster reso

CVE-2026-84196 [HIGH] CWE-918 CVE-2026-84196: Kyverno before 1.18.0 contains a server-side request forgery vulnerability in apiCall.service.url th Kyverno before 1.18.0 contains a server-side request forgery vulnerability in apiCall.service.url that allows authenticated users to send arbitrary HTTP requests by injecting user-controlled input through variable substitution. Attackers can target internal services, cloud metadata endpoints, and loopback addresses, with response data reflected in adm

CVE-2026-41068 [HIGH] CVE-2026-41068: Kyverno is a policy engine designed for cloud native platform engineering teams. The patch for CVE-2 Kyverno is a policy engine designed for cloud native platform engineering teams. The patch for CVE-2026-22039 fixed cross-namespace privilege escalation in Kyverno's `apiCall` context by validating the `URLPath` field. However, the ConfigMap context loader has the identical vulnerability — the `configMap.namespace` field accepts any namespace with zero valida

CVE-2023-33191 [HIGH] CWE-284 CVE-2023-33191: Kyverno is a policy engine designed for Kubernetes. Kyverno seccomp control can be circumvented. Use Kyverno is a policy engine designed for Kubernetes. Kyverno seccomp control can be circumvented. Users of the podSecurity `validate.podSecurity` subrule in Kyverno 1.9.2 and 1.9.3 are vulnerable. This issue was patched in version 1.9.4.

CVE-2022-47633 [HIGH] CWE-287 CVE-2022-47633: An image signature validation bypass vulnerability in Kyverno 1.8.3 and 1.8.4 allows a malicious ima An image signature validation bypass vulnerability in Kyverno 1.8.3 and 1.8.4 allows a malicious image registry (or a man-in-the-middle attacker) to inject unsigned arbitrary container images into a protected Kubernetes cluster. This is fixed in 1.8.5. This has been fixed in 1.8.5 and mitigations are available for impacted releases.

CVE-2026-41485 [HIGH] CWE-617 CVE-2026-41485: Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1 Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1.17.2 and 1.16.4, an unchecked type assertion in the `forEach` mutation handler allows any user with permission to create a `Policy` or `ClusterPolicy` to crash the cluster-wide background controller into a persistent CrashLoopBackOff. The same bug also