Skip to content
Fencer Vulns
medium 6.7

CVE-2025-5187 json

Nodes can delete themselves by adding an OwnerReference

published 2025-08-27 14 mo ago modified 2026-09-10 1 mo ago also EUVD-2025-25937 , GHSA-4x4m-3c2p-qppc , GO-2025-3915

cvss
6.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

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.

Patch / fix

  • go k8s.io/kubernetes 1.31.12, 1.32.8, 1.33.4
  • kubernetes kube-apiserver 1.31.12, 1.32.8, 1.33.4
  • kubernetes Debian 14, Debian 13, Debian 12 1.20.5+really1.20.2-1

debian advisories DEBIAN-CVE-2025-5187

  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250918T182144-150000.1.107.1

suse advisories SUSE-SU-2025:03289-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250918T182144-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15566-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-5187 updated cvss 6.7

kubernetes: kube-apiserver: Nodes can delete themselves by adding an OwnerReference

  • Red Hat OpenShift Container Platform 4 openshift, microshift, microshift-olm, microshift-sriov, microshift-multus, openshift-clients, +28 more
    affected: workaround, no fix available, no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 4.18 openshift4 ose-cluster-kube-apiserver-operator-container-v4.18.0-202509100344.p2.gb6ad4b0.assembly.stream.el9
    fixed: vendor fix RHBA-2025:15714
  • Red Hat OpenShift Container Platform 4.19 openshift4 ose-cluster-kube-apiserver-operator-container-v4.19.0-202509091807.p2.g80c1fc3.assembly.stream.el9
    fixed: vendor fix RHBA-2025:15694
  • Red Hat OpenShift Container Platform 4.18 openshift4 v4.18.0-202509090932.p2.g716eb0e.assembly.stream.el9, openshift4 v4.18.0-202509090932.p2.ga432067.assembly.stream.el9, openshift4 v4.18.0-202509090932.p2.gb4e1047.assembly.stream.el9, openshift4 v4.18.0-202509100344.p2.g01fc505.assembly.stream.el9, openshift4 v4.18.0-202509100344.p2.g0a6f6eb.assembly.stream.el9, openshift4 v4.18.0-202509100344.p2.g18c2332.assembly.stream.el9, +178 more Red Hat OpenShift Container Platform 4.19 openshift4 v4.19.0-202509091807.p2.g059d95c.assembly.stream.el9, openshift4 v4.19.0-202509091807.p2.g06a66db.assembly.stream.el9, openshift4 v4.19.0-202509091807.p2.g0ab3099.assembly.stream.el9, openshift4 v4.19.0-202509091807.p2.g1dbf0c7.assembly.stream.el9, openshift4 v4.19.0-202509091807.p2.g3dfbb67.assembly.stream.el9, openshift4 v4.19.0-202509091807.p2.g3dfcfa1.assembly.stream.el9, +179 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
14 mo ago

Exploit prediction

0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
GitHub 3.1 6.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
go k8s.io/kubernetes
<1.31.12
>=1.32.0-alpha.0, <1.32.8
>=1.33.0-alpha.0, <1.33.4
1.31.12
1.32.8
1.33.4

Affected products

  • Kubernetes Kubernetes

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.