Skip to content

Kubernetes Nodes can delete themselves by adding an OwnerReference

Moderate severity GitHub Reviewed Published Aug 27, 2025 to the GitHub Advisory Database • Updated Aug 27, 2025

Package

gomod k8s.io/kubernetes (Go)

Affected versions

< 1.31.12
>= 1.32.0-alpha.0, < 1.32.7
>= 1.33.0-alpha.0, < 1.33.4

Patched versions

1.31.12
1.32.8
1.33.4

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.

References

Published by the National Vulnerability Database Aug 27, 2025
Published to the GitHub Advisory Database Aug 27, 2025
Reviewed Aug 27, 2025
Last updated Aug 27, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(2nd percentile)

Weaknesses

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Learn more on MITRE.

CVE ID

CVE-2025-5187

GHSA ID

GHSA-4x4m-3c2p-qppc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.