Security loopholes while mapping .kube/config file on to docker as volume


I have a scenario where I have to install Kubernetes on a public cloud and access the Kubernetes via kubectl from a VM on my laptop.

Kubectl accesses .kube/config to connect K8S API-Server to do the required operation.

There is an application that is running as docker inside the VM and connects to K8S using .kube/config that is mapped as volume. That is -v $ HOME/.kube:/home/test/.kube

Is there any security loopholes should I be aware of?