prowler/api/changelog.d/kubeconfig-inline-credentials.security.md

Kubernetes kubeconfig validation accepts only inline credentials and known cluster fields, rejecting file-path fields (tokenFile, client-certificate, client-key, certificate-authority), command-based authentication (exec, cmd-path), auth-provider directives, proxy URLs and unknown user or cluster keys; stored kubeconfigs are re-validated before each scan and connection test