First published: Fri Apr 25 2025(Updated: )
CNCF K3s 1.32 before 1.32.4-rc1+k3s1 has a Kubernetes kubelet configuration change with the unintended consequence that, in some situations, ReadOnlyPort is set to 10255. For example, the default behavior of a K3s online installation might allow unauthenticated access to this port, exposing credentials.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
K3s | <1.32.4-rc1+k3s1 | |
go/github.com/k3s-io/k3s | >=1.32.0-rc1<1.32.4-rc1 | 1.32.4-rc1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-46599 is considered a critical vulnerability due to the potential for unauthorized access to sensitive information.
To fix CVE-2025-46599, upgrade K3s to version 1.32.4-rc1+k3s1 or later, where the ReadOnlyPort is properly configured.
The risks of CVE-2025-46599 include exposing potentially sensitive credentials and information to unauthorized users due to incorrect kubelet configuration.
CVE-2025-46599 affects K3s versions prior to 1.32.4-rc1+k3s1.
Yes, temporarily disabling the ReadOnlyPort can serve as a workaround until a proper upgrade can be applied.