Nodes can delete themselves by adding an OwnerReference
cve-program · CVE-2025-5187
PublishedA 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.
Read the publisher's advisoryeuvd · EUVD-2025-25937
PublishedA 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.
Read the publisher's advisorynvd · CVE-2025-5187
PublishedA 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.
Read the publisher's advisoryosv · GHSA-4x4m-3c2p-qppc
PublishedA 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.
Read the publisher's advisoryosv · GO-2025-3915
PublishedKubernetes Nodes can delete themselves by adding an OwnerReference in k8s.io/kubernetes
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-2025-5187 · CVE overview and exploitation status
cve-program · CVE-2025-5187
- https://github.com/kubernetes/kubernetes/issues/133471
- https://groups.google.com/g/kubernetes-security-announce/c/znSNY7XCztE
euvd · EUVD-2025-25937
- https://github.com/kubernetes/kubernetes/issues/133471
- https://groups.google.com/g/kubernetes-security-announce/c/znSNY7XCztE
nvd · CVE-2025-5187
- https://github.com/kubernetes/kubernetes/issues/133471
- https://groups.google.com/g/kubernetes-security-announce/c/znSNY7XCztE
osv · GHSA-4x4m-3c2p-qppc
- https://nvd.nist.gov/vuln/detail/CVE-2025-5187
- https://github.com/kubernetes/kubernetes/issues/133471
- https://github.com/kubernetes/kubernetes/commit/a2d98cac56a0c5cb2d8abc4d087fc00846b3bc0f
- https://github.com/kubernetes/kubernetes
- https://groups.google.com/g/kubernetes-security-announce/c/znSNY7XCztE
osv · GO-2025-3915
Related changes
Linked by CVE identifierNo related changes are available here.