Kubelet API Accessible Without Authentication
The kubelet API on a node accepts unauthenticated requests, letting anyone who can reach it list pods and run commands in any container on that node.
| Severity | Critical |
| CVSS 3.1 | 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-306: Missing Authentication for Critical Function |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1133 External Remote Services, T1609 Container Administration Command, T1613 Container and Resource Discovery |
| Category | Broken Access Control |
Description
The kubelet, the agent that runs on every Kubernetes node, exposes an HTTPS API, by default on port 10250, which the API server uses to read container logs, run commands in containers and forward ports. If the kubelet accepts anonymous requests and authorises every request, which is what its command-line defaults do (--anonymous-auth=true with --authorization-mode=AlwaysAllow), anyone who can reach the port can use this API: they can list every pod on the node and run commands in any of its containers through the /run and /exec endpoints, without any Kubernetes credentials and without the requests appearing in the API server's audit log.
Commands in containers give access to their data, secrets and service account tokens, and a privileged pod on the node leads to control of the node itself, so every exposed node exposes every workload scheduled on it. Common installers and managed services configure the kubelet more securely, so the weakness is mostly found on manually built, customised or older clusters.
It can be confirmed by requesting the /pods endpoint on port 10250 without credentials: a list of pods confirms the exposure, while 401 Unauthorized shows that anonymous access is disabled. Tools such as kubeletctl automate these checks. The kubelet's read-only port, conventionally 10255, serves pod and node information over plain HTTP without any authentication wherever it is enabled.
Remediation
- Disable anonymous access and delegate authorisation to the API server, in the kubelet configuration file or with the equivalent flags (
--anonymous-auth=false,--authorization-mode=Webhookand--client-ca-file). - Configure the API server to authenticate to kubelets with a client certificate (
--kubelet-client-certificateand--kubelet-client-key) and grant that identity only the kubelet API permissions it needs. - Disable the read-only port by setting
readOnlyPort: 0. - Restrict access to port 10250 on every node to the control plane and the monitoring systems that need it.
Restart the kubelet on each node after the change, then confirm the fix by repeating the unauthenticated requests to ports 10250 and 10255.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.