Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Nodes can delete themselves by adding an OwnerReference

CVSS 3.1 6.7 MEDIUMEUVD CVSS 3.1 6.7 CVSS 3.1 · [email protected] · Secondary 6.7 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by k8s.io/kubernetes 1.31.12Fixed by k8s.io/kubernetes 1.32.8Fixed by k8s.io/kubernetes 1.33.4osv · severity unknownFixed by k8s.io/kubernetes 1.31.12Fixed by k8s.io/kubernetes 1.32.8Fixed by k8s.io/kubernetes 1.33.4KEV status unknown

cve-program · CVE-2025-5187

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-25937

Published

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.

Read the publisher's advisory

nvd · CVE-2025-5187

Published

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.

Read the publisher's advisory

osv · GHSA-4x4m-3c2p-qppc

Published

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.

Read the publisher's advisory

osv · GO-2025-3915

Published

Kubernetes Nodes can delete themselves by adding an OwnerReference in k8s.io/kubernetes

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current