All reports
Medium

Kubernetes Nodes can delete themselves by adding an OwnerReference

Affected versions

Version ranges need review.

Affected versions
< 1.31.12
Fixed version
1.31.12
Affected versions
<1.31.12 || >=1.32.0-alpha.0 <1.32.8 || >=1.33.0-alpha.0 <1.33.4
Fixed version
1.31.12 · 1.32.8 · 1.33.4
Affected versions
>= 1.33.0-alpha.0, < 1.33.4
Fixed version
1.33.4
Affected versions
>= 1.32.0-alpha.0, < 1.32.7
Fixed version
1.32.8
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-5187

Probability of exploitation in the next 30 days: 0.62%

FIRST EPSS · 2026-11-18

Description

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.

Links