Kubernetes Nodes can delete themselves by adding an OwnerReference
A vulnerability exists in the NodeRestriction admission controller in Kubernetes clusters where node users can delete their corresponding node object by patching themselves with an OwnerReference to a cluster-scoped resource. If the OwnerReference resource does not exist or is subsequently deleted, the given node object will be deleted via garbage collection.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-5187US | —OT elevated | — | ||
A vulnerability exists in the NodeRestriction admission controller in Kubernetes clusters where node users can delete their corresponding node object by patching themselves with an… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/kubernetes/kubernetesPACKAGE
- https://github.com/kubernetes/kubernetes/commit/a2d98cac56a0c5cb2d8abc4d087fc00846b3bc0fWEB
- https://github.com/kubernetes/kubernetes/issues/133471WEB
- https://groups.google.com/g/kubernetes-security-announce/c/znSNY7XCztEWEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-5187ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan