CVE-2025-5187

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2025-5187 has a CVSS score of 6.7 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.31.12, 1.32.8, 1.33.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-5187? CVE-2025-5187 is a medium-severity incorrect authorization vulnerability in k8s.io/kubernetes (go), affecting versions < 1.31.12. It is fixed in 1.31.12, 1.32.8, 1.33.4. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2025-5187? CVE-2025-5187 has a CVSS score of 6.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of k8s.io/kubernetes are affected by CVE-2025-5187? k8s.io/kubernetes (go) versions < 1.31.12 is affected.
4. Is there a fix for CVE-2025-5187? Yes. CVE-2025-5187 is fixed in 1.31.12, 1.32.8, 1.33.4. Upgrade to this version or later.
5. Is CVE-2025-5187 exploitable, and should I be worried? Whether CVE-2025-5187 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-5187 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-5187?
   • Upgrade k8s.io/kubernetes to 1.31.12 or later
   • Upgrade k8s.io/kubernetes to 1.32.8 or later
   • Upgrade k8s.io/kubernetes to 1.33.4 or later