Skip to content

kubernetes allows nodes to bypass dynamic resource allocation authorization checks

Low severity GitHub Reviewed Published Jun 23, 2025 to the GitHub Advisory Database • Updated Jun 23, 2025

Package

gomod k8s.io/kubernetes (Go)

Affected versions

>= 1.32.0, <= 1.32.5
>= 1.33.0, <= 1.33.1

Patched versions

1.32.6
1.33.2

Description

A vulnerability exists in the NodeRestriction admission controller where nodes can bypass dynamic resource allocation authorization checks. When the DynamicResourceAllocation feature gate is enabled, the controller properly validates resource claim statuses during pod status updates but fails to perform equivalent validation during pod creation. This allows a compromised node to create mirror pods that access unauthorized dynamic resources, potentially leading to privilege escalation.

References

Published by the National Vulnerability Database Jun 23, 2025
Published to the GitHub Advisory Database Jun 23, 2025
Reviewed Jun 23, 2025
Last updated Jun 23, 2025

Severity

Low

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
None
Integrity
None
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:N/I:N/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.
(3rd percentile)

Weaknesses

CVE ID

CVE-2025-4563

GHSA ID

GHSA-hj2p-8wj8-pfq4

Source code

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