← Back

Kubernetes

kubernetes

Vendor: Kubernetes • 56 CVEs

CVEs (56)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
2Fedoraproject
Kubernetes
2Fedora
Kubernetes
Jan 3, 2025
Nov 14, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
A security issue was discovered in Kubernetes where a user that can create pods and persistent volumes on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if...Show more
A security issue was discovered in Kubernetes where a user that can create pods and persistent volumes on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they are using an in-tree storage plugin for Windows nodes.Show less
1Kubernetes
1Kubernetes
Feb 13, 2025
Oct 31, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Window...Show more
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes.Show less
1Kubernetes
1Kubernetes
Feb 13, 2025
Oct 31, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Window...Show more
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes.Show less
1Kubernetes
1Kubernetes
Jun 12, 2025
Oct 30, 2023
N/A· v4
6.3 MEDIUM· v3
N/A· v2
Kube-proxy on Windows can unintentionally forward traffic to local processes listening on the same port (“spec.ports[*].port”) as a LoadBalancer Service when the LoadBalancer controller does not set the “status.loadB...Show more
Kube-proxy on Windows can unintentionally forward traffic to local processes listening on the same port (“spec.ports[*].port”) as a LoadBalancer Service when the LoadBalancer controller does not set the “status.loadBalancer.ingress[].ip” field. Clusters where the LoadBalancer controller sets the “status.loadBalancer.ingress[].ip” field are unaffected.Show less
1Kubernetes
1Kubernetes
Feb 13, 2025
Jul 3, 2023
N/A· v4
6.5 MEDIUM· v3
N/A· v2
Users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using ephemeral containers. The policy ensures pods running with a service account may...Show more
Users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using ephemeral containers. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the `kubernetes.io/enforce-mountable-secrets` annotation are used together with ephemeral containers.Show less
1Kubernetes
1Kubernetes
Feb 13, 2025
Jul 3, 2023
N/A· v4
6.5 MEDIUM· v3
N/A· v2
Users may be able to launch containers using images that are restricted by ImagePolicyWebhook when using ephemeral containers. Kubernetes clusters are only affected if the ImagePolicyWebhook admission plugin is used toge...Show more
Users may be able to launch containers using images that are restricted by ImagePolicyWebhook when using ephemeral containers. Kubernetes clusters are only affected if the ImagePolicyWebhook admission plugin is used together with ephemeral containers.Show less
2Fedoraproject
Kubernetes
2Fedora
Kubernetes
Dec 12, 2024
Jun 16, 2023
N/A· v4
5.5 MEDIUM· v3
N/A· v2
A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In t...Show more
A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet.Show less
1Kubernetes
1Kubernetes
Nov 21, 2024
May 24, 2023
N/A· v4
7.8 HIGH· v3
N/A· v2
Windows workloads can run as ContainerAdministrator even when those workloads set the runAsNonRoot option to true.
1Kubernetes
1Kubernetes
Nov 21, 2024
Mar 1, 2023
N/A· v4
8.8 HIGH· v3
N/A· v2
Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports node proxyin...Show more
Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this validation could allow authenticated requests destined for Nodes to to the API server's private network.Show less
1Kubernetes
1Kubernetes
Nov 21, 2024
Mar 1, 2023
N/A· v4
6.5 MEDIUM· v3
N/A· v2
Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability...Show more
Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.Show less
1Kubernetes
1Kubernetes
Jun 1, 2026
Feb 1, 2022
N/A· v4
3.1 LOW· v3
3.5 LOW· v2
As mitigations to a report from 2019 and CVE-2020-8555, Kubernetes attempts to prevent proxied connections from accessing link-local or localhost networks when making user-driven connections to Services, Pods, Nodes, or...Show more
As mitigations to a report from 2019 and CVE-2020-8555, Kubernetes attempts to prevent proxied connections from accessing link-local or localhost networks when making user-driven connections to Services, Pods, Nodes, or StorageClass service providers. As part of this mitigation Kubernetes does a DNS name resolution check and validates that response IPs are not in the link-local (169.254.0.0/16) or localhost (127.0.0.0/8) range. Kubernetes then performs a second DNS resolution without validation for the actual connection. If a non-standard DNS server returns different non-cached responses, a user may be able to bypass the proxy IP restriction and access private networks on the control plane.Show less
1Kubernetes
1Kubernetes
Jan 13, 2026
Jan 7, 2022
N/A· v4
3.0 LOW· v3
2.1 LOW· v2
kubectl does not neutralize escape, meta or control sequences contained in the raw data it outputs to a terminal. This includes but is not limited to the unstructured string fields in objects such as Events.
1Kubernetes
1Kubernetes
Nov 21, 2024
Sep 20, 2021
N/A· v4
8.1 HIGH· v3
5.5 MEDIUM· v2
A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem.
1Kubernetes
1Kubernetes
Jun 1, 2026
Sep 20, 2021
N/A· v4
3.1 LOW· v3
3.5 LOW· v2
A security issue was discovered with Kubernetes that could enable users to send network traffic to locations they would otherwise not have access to via a confused deputy attack.
1Kubernetes
1Kubernetes
Jun 1, 2026
Sep 20, 2021
N/A· v4
4.1 MEDIUM· v3
4.0 MEDIUM· v2
A security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private net...Show more
A security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, they can view the redirected responses and headers in the logs.Show less
1Kubernetes
1Kubernetes
Nov 21, 2024
Sep 6, 2021
N/A· v4
4.8 MEDIUM· v3
4.9 MEDIUM· v2
A security issue was discovered in Kubernetes where a user may be able to redirect pod traffic to private networks on a Node. Kubernetes already prevents creation of Endpoint IPs in the localhost or link-local range, but...Show more
A security issue was discovered in Kubernetes where a user may be able to redirect pod traffic to private networks on a Node. Kubernetes already prevents creation of Endpoint IPs in the localhost or link-local range, but the same validation was not performed on EndpointSlice IPs.Show less
1Kubernetes
1Kubernetes
Nov 21, 2024
Sep 6, 2021
N/A· v4
6.5 MEDIUM· v3
5.5 MEDIUM· v2
A security issue was discovered in kube-apiserver that could allow node updates to bypass a Validating Admission Webhook. Clusters are only affected by this vulnerability if they run a Validating Admission Webhook for No...Show more
A security issue was discovered in kube-apiserver that could allow node updates to bypass a Validating Admission Webhook. Clusters are only affected by this vulnerability if they run a Validating Admission Webhook for Nodes that denies admission based at least partially on the old state of the Node object. Validating Admission Webhook does not observe some previous fields.Show less
2Kubernetes
Oracle
4Communications Cloud Native Core Network Slice Selection Function
Communications Cloud Native Core PolicyCommunications Cloud Native Core Service Communication Proxy+1 more
Jun 1, 2026
Jan 21, 2021
N/A· v4
5.0 MEDIUM· v3
6.0 MEDIUM· v2
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patc...Show more
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typically be granted to users) of a LoadBalancer service can set the status.loadBalancer.ingress.ip to similar effect.Show less
1Kubernetes
1Kubernetes
Nov 21, 2024
Dec 7, 2020
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
In Kubernetes clusters using Ceph RBD as a storage provisioner, with logging level of at least 4, Ceph RBD admin secrets can be written to logs. This occurs in kube-controller-manager's logs during provisioning of Ceph R...Show more
In Kubernetes clusters using Ceph RBD as a storage provisioner, with logging level of at least 4, Ceph RBD admin secrets can be written to logs. This occurs in kube-controller-manager's logs during provisioning of Ceph RBD persistent claims. This affects < v1.19.3, < v1.18.10, < v1.17.13.Show less
1Kubernetes
1Kubernetes
Nov 21, 2024
Dec 7, 2020
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects <= v1.19.3,...Show more
In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects <= v1.19.3, <= v1.18.10, <= v1.17.13, < v1.20.0-alpha2.Show less