CveMateVulnerability intelligence

Kubernetes vulnerabilities, page 2

124 vulnerabilities

Known vulnerabilities in Kubernetes products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 36 products.

CVE-2015-7528github.com/kuberneteskubernetes+1810y ago11-04-2016 21:00

Kubernetes before 1.2.0-alpha.5 allows remote attackers to read arbitrary pod logs via a container name.CVE-2015-7561chainguardkubernetes-1.30+149y ago07-08-2017 17:00

Kubernetes in OpenShift3 allows remote authenticated users to use the private images of other users should they know the name of said image.CVE-2016-1906chainguardkubernetes-1.30+1310y ago03-02-2016 15:00

Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that is not allowed.CVE-2016-1905chainguardkubernetes-1.30+1310y ago03-02-2016 15:00

The API server in Kubernetes does not properly check admission control, which allows remote authenticated users to access additional resources via a crafted patched object.CVE-2016-7075chainguardkubernetes-1.30+278y ago10-09-2018 14:00

It was found that Kubernetes as used by Openshift Enterprise 3 did not correctly validate X.509 client intermediate certificate host name fields. An attacker could use this flaw to bypass authentication requirements by using a specially crafted X.509 certificate.CVE-2025-13281chainguardargo-cd-2.13+36110mo ago14-12-2025 21:27

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).CVE-2025-1767chainguardargo-cd-2.11+7211y ago13-03-2025 16:40

This CVE only affects Kubernetes clusters that utilize the in-tree gitRepo volume to clone git repositories from other pods within the same node. Since the in-tree gitRepo volume feature has been deprecated and will not receive security updates upstream, any cluster still using this feature remains vulnerable.CVE-2025-1098chainguardingress-nginx-controller-1.12+161y ago24-03-2025 23:29

A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `mirror-target` and `mirror-host` Ingress annotations can be used to inject arbitrary configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)CVE-2025-1974chainguardingress-nginx-controller-1.12+251y ago24-03-2025 23:28

A security issue was discovered in Kubernetes where under certain conditions, an unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller. This can lead to disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)CVE-2025-1097chainguardingress-nginx-controller-1.12+161y ago24-03-2025 23:29

A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-cn` Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)CVE-2025-0426chainguardargo-cd-2.11+2661y ago13-02-2025 15:16

A security issue was discovered in Kubernetes where a large number of container checkpoint requests made to the unauthenticated kubelet read-only HTTP endpoint may cause a Node Denial of Service by filling the Node's disk.CVE-2025-9708chainguardkubernetes-reflector+51y ago16-09-2025 21:08

A vulnerability exists in the Kubernetes C# client where the certificate validation logic accepts properly constructed certificates from any Certificate Authority (CA) without properly verifying the trust chain. This flaw allows a malicious actor to present a forged certificate and potentially intercept or manipulate communication with the Kubernetes API server, leading to possible man-in-the-middle attacks and API impersonation.CVE-2025-4563chainguardargo-cd-3.0+1471y ago23-06-2025 15:38

A vulnerability exists in the NodeRestriction admission controller where nodes can bypass dynamic resource allocation authorization checks. When the DynamicResourceAllocation feature gate is enabled, the controller properly validates resource claim statuses during pod status updates but fails to perform equivalent validation during pod creation. This allows a compromised node to create mirror pods that access unauthorized dynamic resources, potentially leading to privilege escalation.CVE-2025-7445sigs.k8s.iosecrets-store-sync-controller+11y ago05-09-2025 02:31

Kubernetes secrets-store-sync-controller in versions before 0.0.2 discloses service account tokens in logs.CVE-2025-7342kubernetesimage builder1y ago17-08-2025 23:03

A security issue was discovered in the Kubernetes Image Builder where default credentials are enabled during the Windows image build process when using the Nutanix or VMware OVA providers. These credentials, which allow root access, are disabled at the conclusion of the build. Kubernetes clusters are only affected if their nodes use VM images created via the Image Builder project and the vulnerability was exploited during the build process, which requires an attacker to access the build VM and modify the image while the build is in progress.CVE-2025-5187chainguardargo-cd-2.13+2201y ago27-08-2025 16:20

A vulnerability exists in the NodeRestriction admission controller in Kubernetes clusters where node users can delete their corresponding node object by patching themselves with an OwnerReference to a cluster-scoped resource. If the OwnerReference resource does not exist or is subsequently deleted, the given node object will be deleted via garbage collection.CVE-2025-24513chainguardingress-nginx-controller-1.12+161y ago24-03-2025 23:29

A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where attacker-provided data are included in a filename by the ingress-nginx Admission Controller feature, resulting in directory traversal within the container. This could result in denial of service, or when combined with other vulnerabilities, limited disclosure of Secret objects from the cluster.CVE-2025-24514chainguardingress-nginx-controller-1.12+161y ago24-03-2025 23:29

A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)CVE-2025-15566kubernetesingress-nginx8mo ago06-02-2026 03:13

A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/auth-proxy-set-headers` Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)CVE-2020-8563ubuntukubernetes+55y ago07-12-2020 22:00

In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.