CVE-2025-5187GHSA-4X4M-3C2P-QPPCGO-2025-3915
Nodes can delete themselves by adding an OwnerReference
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.31.12, 1.32.8, 1.33.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Kubernetes Kubernetes
From v1.31.0 · through v1.31.11; From v1.32.0 · through v1.32.7; From v1.33.0 · through v1.33.3
- k8s.io/kubernetesGo
fixed in 1.31.12
- k8s.io/kubernetesGo
From 1.32.0-alpha.0 · fixed in 1.32.8
- k8s.io/kubernetesGo
From 1.33.0-alpha.0 · fixed in 1.33.4
- k8s.io/kubernetesGo
fixed in 1.31.12; From 1.32.0-alpha.0 · fixed in 1.32.8; From 1.33.0-alpha.0 · fixed in 1.33.4