As mitigations to a report from 2019 and CVE-2020-8555, Kubernetes attempts to prevent proxied connections…
Historical advisory recorded 24 Oct 2026 17:17:27 UTC. Read the latest advisory.
nvd · CVE-2020-8562
PublishedAs mitigations to a report from 2019 and CVE-2020-8555, Kubernetes attempts to prevent proxied connections from accessing link-local or localhost networks when making user-driven connections to Services, Pods, Nodes, or StorageClass service providers. As part of this mitigation Kubernetes does a DNS name resolution check and validates that response IPs are not in the link-local (169.254.0.0/16) or localhost (127.0.0.0/8) range. Kubernetes then performs a second DNS resolution without validation for the actual connection. If a non-standard DNS server returns different non-cached responses, a user may be able to bypass the proxy IP restriction and access private networks on the control plane.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2020-8562 · CVE overview and exploitation status
nvd · CVE-2020-8562
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.