CVE-2020-8555: Server Side Request Forgery (SSRF) in Kubernetes
Summary
CVE-2020-8555: Server Side Request Forgery (SSRF) in Kubernetes. Affects k8s.io/kubernetes across 4 version ranges.
< 1.15.12
>= 1.16.0, < 1.16.9
>= 1.17.0, < 1.17.4
>= 1.18.0, < 1.18.1
Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓
Also tracked for
- kubernetes · Debian:11
The same CVE-2020-8555 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Kubernetes is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. It consists of various components, including the kube-controller-manager, which is responsible for managing different controllers that regulate the state of the cluster. One of the functionalities of kube-controller-manager is to handle volume storage operations, such as the storageos package in the Go ecosystem.
Vulnerability Detail
The Kubernetes kube-controller-manager versions v1.0-1.14, prior to v1.15.12, v1.16.9, v1.17.5, and v1.18.0 are susceptible to a Server Side Request Forgery (SSRF) vulnerability. This vulnerability allows certain authorized users to exploit unprotected endpoints within the master's host network, potentially leaking up to 500 bytes of arbitrary information. These unprotected endpoints can include link-local or loopback services, posing a risk of unauthorized data exposure.
How To Fix
Latest published version: v1.37.1 as of 23 Oct 2026
go get k8s.io/kubernetes@v1.37.1Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.15.121.15.12go get k8s.io/kubernetes@v1.15.12 -
>= 1.16.0, < 1.16.91.16.9go get k8s.io/kubernetes@v1.16.9 -
>= 1.17.0, < 1.17.41.17.4go get k8s.io/kubernetes@v1.17.4 -
>= 1.18.0, < 1.18.11.18.1go get k8s.io/kubernetes@v1.18.1
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. However, implementing network-level access controls and restrictions can help mitigate the risk of unauthorized access to unprotected endpoints. It is advised to review and update the network policies and configurations to limit access to sensitive services and endpoints.
Conclusion
The Server Side Request Forgery (SSRF) vulnerability in Kubernetes can potentially lead to unauthorized data exposure and information leakage. It is crucial to upgrade to the fixed versions of Kubernetes and apply security patches to mitigate this risk. Implementing network-level access controls and restrictions can further enhance the security posture. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for k8s.io/kubernetes →
FAQ
Kubernetes is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications.
kube-controller-manager is a component of Kubernetes responsible for managing different controllers that regulate the state of the cluster.
Server Side Request Forgery (SSRF) is a vulnerability that allows an attacker to make requests from the server to other internal or external resources, potentially leading to unauthorized data exposure or attacks on internal systems.
This vulnerability can result in the leakage of up to 500 bytes of arbitrary information from unprotected endpoints within the master's host network. This information could include sensitive data or credentials, leading to potential data breaches or unauthorized access.
To mitigate the risk, it is recommended to upgrade to the fixed versions of Kubernetes and regularly apply security patches. Additionally, implementing network-level access controls and restrictions can help limit access to unprotected endpoints.
References
Related vulnerabilities
Recent vulnerabilities recorded for k8s.io/kubernetes.
