CVE-2018-1002105Critical· 9.8▾ AbyssalPoC availablePrivilege Escalation in Kubernetes
▾ Abyssal zone — Critical with a public exploit or in-the-wild use
impact 53.9 · likelihood 17.4 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 2 sources. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
87%
Exploit-DB · 5 GitHub repos (last check)
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.
github.com/kubernetes/kubernetes < 1.10.11github.com/kubernetes/kubernetes >= 1.11.0, < 1.11.5github.com/kubernetes/kubernetes >= 1.12.0, < 1.12.3Upgrade to a patched release:
github.com/kubernetes/kubernetes 1.10.11github.com/kubernetes/kubernetes 1.11.5github.com/kubernetes/kubernetes 1.12.3Connected by shared product, vendor, weakness, or advisory.
CVE-2019-1002101Medium· 5.5Symlink Attack in kubectl cp
CVE-2024-10220High· 8.1Kubernetes kubelet arbitrary command execution
CVE-2024-5321Medium· 6.1Kubernetes sets incorrect permissions on Windows containers logs
CVE-2023-3676High· 8.8Kubernetes privilege escalation vulnerability
CVE-2020-8561Medium· 4.1Confused Deputy in Kubernetes
CVE-2025-1767Medium· 6.5Kubernetes GitRepo Volume Inadvertent Local Repository Access